Bug#409347: marked as done (kernel: rsync create bad file on udf filesystem)
Your message dated Thu, 2 Aug 2007 18:25:34 +0200
with message-id <20070802162534.GK9582@stro.at>
and subject line kernel: rsync create bad file on udf filesystem
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: kernel: rsync create bad file on udf filesystem
- From: Jean-Michel <jeanmichel.123@free.fr>
- Date: Fri, 02 Feb 2007 09:34:07 +0100
- Message-id: <20070202083407.6617.97681.reportbug@simi.internal.isoscope.com>
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
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-amd64
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---
- To: 409347-done@bugs.debian.org
- Subject: kernel: rsync create bad file on udf filesystem
- From: maximilian attems <max@stro.at>
- Date: Thu, 2 Aug 2007 18:25:34 +0200
- Message-id: <20070802162534.GK9582@stro.at>
Version: 2.6.18-4
an important udf fix was incorporated,
bug reporter didn't answer on subsequent ping.
if the bug still exists with latest etch kernel please
holler and try out 2.6.21 from backports.org.
--
maks
--- End Message ---
Reply to: