[prev in list] [next in list] [prev in thread] [next in thread]
List: busybox
Subject: Re: Umount issue on upfrading
From: Stephen Beaver <sbeaver () columbus ! rr ! com>
Date: 2007-06-29 16:39:10
Message-ID: C2AAADEE.FA72%sbeaver () columbus ! rr ! com
[Download RAW message or body]
Unfortunately, I don't have strace on my system, but the good news is that
this morning I downloaded 1.2.2 and the problem went away. I am now able to
unmount without error.
I have been testing the new(er) version this morning and it is great to see
so many improvements. I had previously include Debian fuser, telnetd,
udhcpc, stat and unzip because of some issues with the BB version. All of
those issues seem to have been fixed and so I can remove the external
packages from my system.
Thanks!
Steve
On 6/29/07 12:33 PM, "Denis Vlasenko" <vda.linux@googlemail.com> wrote:
> On Thursday 28 June 2007 17:52, Stephen Beaver wrote:
>> ARM based (EP9301) system with Cirrus logic "crater" distro. Kernel 2.6.17 &
>> BB 1.1.3
>>
>> On upgrading from an earlier system (2.4.21 & an early BB), I find that I
>> can no longer make umount work.
>>
>> This is what I see:
>>
>> # mkdir /mnt/temp
>> # mount -t jffs2 /dev/mtdblock3 /mnt/temp
>> # mount
>> # <SNIP>
>> # /dev/mtdblock3 on /mnt/temp type jffs2 (rw)
>>
>> So far so good. An "ls" on /mnt/temp displays the files that are on that
>> device. But ...
>>
>>
>> # umount /dev/mtdblock3
>> # umount: Couldn't umount /dev/mtdblock3: Inappropriate ioctl for device
>>
>> I have been unable to find a cause for this error.
>
>
> Can you do
>
> strace -o umount.log umount /dev/mtdblock3
>
> and send log to list?
> --
> vda
_______________________________________________
busybox mailing list
busybox@busybox.net
http://busybox.net/cgi-bin/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic