Re: [Jfs-discussion] Repaired file system still marked dirty, exit code 4

[Dave K. <dav...@or...>]

On 07/23/2012 12:12 PM, Tim Nufire wrote:
> Dave,
> 
> A quick update on this issue..  I've run jfs_fsck repairs several more times on this file system and each time one more file is deleted due to cross linked blocks. All the files in question were created on the same day and at least 2 of the 3 recent files were corrupt *before* they were deleted. I've since checked all the files created on the same day and 4 out of 1,267 are corrupt. This gives me hope that running jfs_fsck 4 more times will fix the file system. It would be faster to just go in and remove the corrupt files by hand but since the file system is marked dirty I can only mount it read-only.. Is there a way to force it to be read-write? If this is possible, how dangerous would it be to remove the 4 corrupt files manually?

You could use jfs_debugfs to set the superblock state to clean. The
commands are:
sup
m 12 0
x
q

I think under the circumstances, this should be safe.