Hi! I'm sending a fix to e2fsck that forces the filesystem checks to happen when the orphan file is present in the filesystem. This patch resulted from a bug reported in openSUSE Tumbleweed[1] where e2fsck doesn't clean-up this file and later the filesystem fails to be mounted read-only (because it still requires recovery). I'm also sending a new test to validate this scenario. [1] https://bugzilla.suse.com/show_bug.cgi?id=1226043 Luis Henriques (SUSE) (2): e2fsck: don'k skip checks if the orphan file is present in the filesystem tests: new test to check that the orphan file is cleaned up e2fsck/unix.c | 4 ++++ tests/f_clear_orphan_file/expect.1 | 35 +++++++++++++++++++++++++++++ tests/f_clear_orphan_file/expect.2 | 7 ++++++ tests/f_clear_orphan_file/image.gz | Bin 0 -> 12449 bytes tests/f_clear_orphan_file/name | 1 + tests/f_clear_orphan_file/script | 2 ++ 6 files changed, 49 insertions(+) create mode 100644 tests/f_clear_orphan_file/expect.1 create mode 100644 tests/f_clear_orphan_file/expect.2 create mode 100644 tests/f_clear_orphan_file/image.gz create mode 100644 tests/f_clear_orphan_file/name create mode 100644 tests/f_clear_orphan_file/script
