[Bug 217888] jbd2: potential data lost in recovering journal raced with synchronizing fs bdev

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=217888

--- Comment #2 from Zhihao Cheng (chengzhihao1@huawei.com) ---
1. Apply diff_v2 and compile kernel
2. dd if=disk of=/dev/sda bs=1M
3. mount /dev/sda temp # will stuck
4. sync /dev/sda # Type this command in another terminal, finish it in 5s when
you see "wait sync" from dmesg.
4. umount temp
5. fsck.ext4 -fa /dev/sda
/dev/sda: Unattached inode 13


/dev/sda: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)


===============
'touch file' is recorded in journal of sda, and the journal is not replayed
yet.

journal in sda:

Journal starts at block 1, transaction 2
Found expected sequence 2, type 1 (descriptor block) at block 1
Dumping descriptor block, sequence 2, at block 1:
  FS block 84 logged at journal block 2 (flags 0x0)
  FS block 2 logged at journal block 3 (flags 0x2)
  FS block 89 logged at journal block 4 (flags 0x2)  # new inode
  FS block 86 logged at journal block 5 (flags 0x2)
  FS block 726 logged at journal block 6 (flags 0x2) # new dentry
  FS block 1 logged at journal block 7 (flags 0x2)
  FS block 83 logged at journal block 8 (flags 0xa)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.