On 4/26/2011 5:40 PM, Ron Johnson wrote:
But not being able to fsck the fs that I just created is unacceptable.
Again, 'xfs_repair -n' is functionally equivalent to 'xfs_check'. They are two methods (paths) that (should) arrive at the same result. Either will let you know if the filesystem has errors.
Have you run 'xfs_repair -n' yet to see if it trips over your per process memory limit? If it doesn't, you have your fsck and can eat it too. ;)
-- Stan