Arch Linux

TheGrudge

Member

Registered: 2006-06-15

Posts: 206

Website

EXT4 bug when using fsck -D

Well thanks for just closing my thread: http://bbs.archlinux.org/viewtopic.php?pid=571595
If you think that nobody is allowed to say something in this forum, close half off the Off-Topic posts as well.

Anyway I found a bug that is reproducible nearly all the time.
Start fsck with the -D flag to optimize directory layout.

fsck -Df LABEL=xxx

After a successful run, call fsck again, without the -D flag

fsck -f LABEL=xxx

You will get many

Inode XXX has a extra size (136) which is invalid

messages. Can anyone confirm this?
If so, I will report it on http://bugzilla.kernel.org/.

---

digiKam developer - www.digikam.org

foutrelis

Developer

From: Athens, Greece

Registered: 2008-07-28

Posts: 705

Website

Re: EXT4 bug when using fsck -D

I wasn't able to reproduce the behavior you're describing. Mind you, I'm using the 2.6.30 kernel from [testing].

TheGrudge

Member

Registered: 2006-06-15

Posts: 206

Website

Re: EXT4 bug when using fsck -D

Maybe it is a e2fsprogs problem?

I'm running kernel 2.6.29.4 and e2fsprogs 1.41.6.
Right now I can't reproduce it either. It seems to happen when I worked quite some time with the partition, moving files around etc.
When I run the fsck commands from the above post, I get those warnings.
Maybe it is only happening when fsck really optimizes the directory layout? It doesn't seem to happen every time you call the command.

Also note that I'm mounting my ext4 partitions with noatime,barrier=0,nodelalloc...

Last edited by TheGrudge (2009-06-20 17:16:11)

---

digiKam developer - www.digikam.org