Bug#572453: e2fsprogs: e2fsck -D corrupts ext4 when files begin with % or #

2010-03-07 Thread Linas Žvirblis
Package: e2fsprogs Version: 1.41.10-1 I was just hit by this bug. Just wanted to add that directories and files that were relocated to lost+found did not begin with either % or #. Although most (not all) of them had non-ascii characters in the names. It is possible that some of my files got

Bug#572453: e2fsprogs: e2fsck -D corrupts ext4 when files begin with % or #

2010-03-04 Thread Jan Fricke
Package: e2fsprogs Version: 1.41.10-1 Severity: important After e2fsck -D a second e2fsck reports that in some directories . and .. are not the first entries. This happens in directories with entries beginning with % or #. These entries will be connected to lost+found while repairing the file

Bug#572453: e2fsprogs: e2fsck -D corrupts ext4 when files begin with % or #

2010-03-04 Thread tytso
On Thu, Mar 04, 2010 at 12:18:53PM +0100, Jan Fricke wrote: Package: e2fsprogs Version: 1.41.10-1 Severity: important After e2fsck -D a second e2fsck reports that in some directories . and .. are not the first entries. This happens in directories with entries beginning with % or #. These