Andrew Morton wrote: > So it's 100% scriptable and can be left running overnight, etc. It found > quite a few problems with ext3/jbd recovery which I doubt could be found by > other means. This was 6-7 years ago and I'd expect that new recovery bugs > have crept in since then which it can expose. > > I think we should implement this in a formal, mergeable fashion, as there > are numerous filesystems which could and should use this sort of testing > infrastructure. FWIW, xfs has something vaguely similar, the XFS_IOC_GOINGDOWN ioctl, which invokes xfs_fs_goingdown, which takes a few flags: /* * Flags for going down operation */ #define XFS_FSOP_GOING_FLAGS_DEFAULT 0x0 /* going down */ #define XFS_FSOP_GOING_FLAGS_LOGFLUSH 0x1 /* flush log but not data */ #define XFS_FSOP_GOING_FLAGS_NOLOGFLUSH 0x2 /* don't flush log nor data */ but ultimately calls xfs_force_shutdown, which is sort of rougly similar to ext3_abort.... The xfs qa tests make use of this ioctl. -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
