reassign 409347 linux-2.6 stop [ keep the bug report on cc, that is _not_ private mail ]
On Sat, Feb 03, 2007 at 12:31:36AM +0100, [EMAIL PROTECTED] wrote: > Quoting maximilian attems <[EMAIL PROTECTED]>: > > > reassign 409347 linux-image-2.6.18-amd64 > > tags 409347 moreinfo > > stop > > > > On Fri, Feb 02, 2007 at 09:34:07AM +0100, Jean-Michel wrote: > > > Package: kernel > > > Severity: normal > > > > > After doing an > > > rsync -r --max-size=600M /partages/users/Restauration > > > $DEST/........_............_......./ > > > > > > Some inodes seems corrupted: > > > > > > ls -l /mnt/iomega/............./#Root/gay > > > > > > drwxr-x--- 4 root root 696 2007-02-01 21:35 lebel > > > drwxr-x--- 2 root root 40 2007-02-01 22:13 lost+found > > > ?--------- ? ? ? ? ? > > > /mnt/iomega/............./#Root/gay > > > drwxr-x--- 2 root root 372 2007-02-01 22:21 sauvegardes > > > > which fs? > > As in the mail subject line: > udf on a 33 giga bytes iomega removable cartridge > > > send the output of > > cat /etc/fstab > > This file does not conatin /dev/hda /mnt/iomega > > > mount > > I cannot do it now, sorry. > However, it should be something such as > /dev/hda /mnt/iomega udffs rw > > > which steps are needed to reproduce it, > > i do not know. > I just know I have the bug twice today. > The bug occured while doing a rsync with about 20Gbytes date, and one find in > the same time. > > In fact, I do not know if the bug is related to rsync, or to udf. > Might be related to a <control C> I did on rsync, to stop it. > > However, I know that I do not know how to remvove this bad inode. > > > please upgrade also to the latest linux-image from unstable, > > it has quite some updates. > > I cannot do this, or not easily. Sorry. you'd better do it, as linux-image-2.6.18-4-amd64 has an important udf fix. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
