Hi,

I saw the same behaviour here, accessing a Lexar 4Gb firefly drive under
Gnome.

Initially put down to user error, after seeing this bug I tried again
and confirmed the bug: I inserted the USB stick which Gnome mounted for
me, copied a folder 'data' containing 24 files totalling a little under
4Mb, unmounted and re-mounted the drive as root; it contained an empty
"data" folder.

Copied the folder again (as root), ran "sync", unmounted and remounted;
the volume was mounted read-only, with the following kernel messages:
[1808059.588790] FAT: utf8 is not a recommended IO charset for FAT
filesystems, filesystem will be case sensitive!
[1808059.831298] FAT: Filesystem panic (dev sdb1)
[1808059.831298]     fat_get_cluster: invalid cluster chain (i_pos 0)
[1808059.831298]     File system has been set read-only
[1808059.928105] FAT: Filesystem panic (dev sdb1)
[1808059.928105]     fat_get_cluster: invalid cluster chain (i_pos 0)
[1808059.928680] FAT: Filesystem panic (dev sdb1)
[1808059.928680]     fat_get_cluster: invalid cluster chain (i_pos 0)
[1808066.051727] FAT: Filesystem panic (dev sdb1)
[1808066.051733]     fat_get_cluster: invalid cluster chain (i_pos 0)
[1808066.338154] FAT: Filesystem panic (dev sdb1)
[1808066.338160]     fat_get_cluster: invalid cluster chain (i_pos 0)
[1808067.365064] FAT: Filesystem panic (dev sdb1)
[1808067.365064]     fat_get_cluster: invalid cluster chain (i_pos 0)
[1808085.401633] FAT: Filesystem panic (dev sdb1)
[1808085.401638]     fat_get_cluster: invalid cluster chain (i_pos 0)
[1808104.819785] FAT: Filesystem panic (dev sdb1)
[1808104.819785]     fat_get_cluster: invalid cluster chain (i_pos 0)
[1808156.203844] FAT: Filesystem panic (dev sdb1)
[1808156.203844]     fat_get_cluster: invalid cluster chain (i_pos 0)
[1808156.203844]     File system has been set read-only

The 'data' directory showed up with '?' for all permissions, and wasn't
readable.

I ran mkdosfs on the thumbdrive and re-tried mount; cp, sync; umount;
mount.  This time it vworked, so I'm guessing that the corruption likely
initially occured during the initial "failed" cp operation as user, and
was compunded when the directory was overwritten during the subsequent
cp as root.

The initial mount and cp was performed as an unprivileged user from the
Gnome desktop; all subsequent operations were done as root.

More or less stock Lenny install, with linux-image-2.6.26-2-686 version
2.6.26-21lenny4 and mount 2.13.1.1-1


John Pearson

-- 
jo...@gtagalenco.com.au  |   The greatest problem in communication is
Network Administrator    | the illusion that it has been accomplished
+61 4 0739 1169          |   - George Bernard Shaw: The Sanity of Art




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to