![]() | |||||||||||||
Messages in this thread |
On Thursday October 11, rmack@mackman.net wrote: > I was curious if anyone has previosly considered adding a raid-stop > functionality to the magic sysrq command? I realize that a full raid-stop > would make the partition unavailable for read-only access, which may > require the system to be immediately reset. Is there a mechanism to > remount a raid device read-only if all mounts from it are read-only (i.e., > marking the raid superblock clean, syncing, and then only allowing > read-only access)? > > Thanks, Ryan This is a nice idea... but awkward. Particularly if md.o is a module, setting the hooks up properly would not be tidy. What we really need is a general concept of setting all drvies to read-only through the block-dev layer.... maybe in the big blockdev rewrite that is planned for 2.5... NeilBrown > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:08 [from the cache] ©2003-2008 | |||||||||||||