XO-1.75 Q4B12ja (svn 2623) leaves an ext2 filesystem inconsistent after a file delete

[Quozl]

After test 0023 glob file copy in the ext2test.fth the filesystem is left in an inconsistent state as reported by e2fsck on build 881:

bash-4.1# e2fsck -f /dev/sda1
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry 'f.tst' in / (2) has deleted/unused inode 26.  Clear<y>? 

It is the last file deleted in the script that is affected.

Tested on a 128MB and a 2GB USB flash drive.

The minimum reproducer is an olpc.fth file containing:

\ OLPC

to-file u:\f.tst cr
del u:\f.tst

Adding a dir u:\ command to the end of the reproducer prevents the symptom. Theory: a cache is flushed.

Entering the commands interactively instead of using \boot\olpc.fth makes no difference to the symptom.

Deleting a pre-existing file does not produce the symptom.

[wmb@…]

I just noticed that the mkfs command in ext2test.sh is using the -j option, thus creating a journal and making it ext3. OFW doesn't support ext3 with dirty journals (I'm working on that feature right now, but existing releases don't do journals). If the journal is dirty, OFW will definitely have problems with the file system.

[Quozl]

The filesystem was created without -j option, using my earlier script (attached) from which ext2test.sh was derived.

[wmb@…]

Fixed by svn 2795. The problem was actually in the file-system-independent "$delete1" command; it was leaving a handle open, preventing data from being flushed at a much later time.

[Quozl]

Reproduced on Q4C11. Tested fixed in Q4C11ja. Thanks! Closing.

[Quozl]

Fixed in Q4C12.