/forcefsck doesn't add '-f' argument to fsck (for ext4, ext3, ext2)
Bug #435707 reported by
Richard Hansen
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
Binary package hint: mountall
In Jaunty, putting a file named 'forcefsck' in the root directory triggered a filesystem check the next time the computer booted. Now /forcefsck appears to be ignored.
Changed in mountall (Ubuntu): | |
status: | New → Fix Committed |
summary: |
- /forcefsck is ignored + /forcefsck doesn't check root filesystem when passno=0 |
summary: |
- /forcefsck doesn't add '-f' argument to fsck.ext4 + /forcefsck doesn't add '-f' argument to fsck.ext4, fsck.ext3, fsck.ext2 |
summary: |
- /forcefsck doesn't add '-f' argument to fsck.ext4, fsck.ext3, fsck.ext2 + /forcefsck doesn't add '-f' argument to fsck (for ext4, ext3, ext2) |
To post a comment you must log in.
Could you add "set -x" after the "script" line in /etc/init/ mountall. conf and capture the output somehow?
As you can see, this job does attempt to honour the /forcefsck file