On Sat, Feb 24, 2018 at 11:56:44AM -0600, Eric Sandeen wrote: > On 2/24/18 5:23 AM, Yang Joseph wrote: > > hello, > > > > Before the repair process, xfs_repair will check if user specified device already > > has a writable mountpoint. And it will stat all the mountpoints of the system. If there > > is a dead mountpoint, this checking will be blocked and xfs_repair will enter 'D' state. So why is the mount point dead? That kinda means that the filesystem is still mounted, but something has hung somewhere and the filesystem may still have active references to the underlying device and be doing stuff that is modifying the filesystem.... And if the device is still busy, then you aren't going to be able to mount the repaired device, anyway, because the block device is still busy... > That sounds like a bug worth fixing, but I am much > less excited about adding options which could do serious damage > to a filesystem. TO me it sounds like something that should be fixed by a reboot, not by adding dangerous options to xfs_repair... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
