On Feb 5 2007 18:32, Christoph Hellwig wrote: > >in two recent discussions (file_list_lock scalability and remount r/o >on suspend) I stumbled over this emergency remount feature. It's not >actually useful because it tries a potentially dangerous remount >despite writers still beeing in progress, which we can't get rid. The current way is to remount things, and return -EROFS to any process that attempts to write(). Unless we want to kill processes to get rid of them [most likely we possibly won't], I am fine with how things are atm. So, what's the "dangerous" part, actually? >Any ideas and comments? sysrq+u is helpful. It is like \( sysrq+s && make sure no further writes go to disk \). Jan -- - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
