path: root/fs/ext3/super.c
diff options
authorToshiyuki Okajima <toshi.okajima@jp.fujitsu.com>2011-08-02 18:16:57 +0900
committerJan Kara <jack@suse.cz>2011-08-17 11:41:20 +0200
commit1cde201da4e97f10a5dd2434cff4ceff381603d1 (patch)
tree065b3fc2b2cb29f16af7af2f297bec66896655f2 /fs/ext3/super.c
parentext3: Remove i_mutex from ext3_sync_file() (diff)
ext3: fix message in ext3_remount for rw-remount case
If there are some inodes in orphan list while a filesystem is being read-only mounted, we should recommend that peole umount and then mount it when they try to remount with read-write. But the current message and comment recommend that they umount and then remount it which may be slightly misleading. Signed-off-by: Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com> Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to '')
1 files changed, 2 insertions, 2 deletions
diff --git a/fs/ext3/super.c b/fs/ext3/super.c
index 7beb69ae0015..2043bcc87719 100644
--- a/fs/ext3/super.c
+++ b/fs/ext3/super.c
@@ -2669,13 +2669,13 @@ static int ext3_remount (struct super_block * sb, int * flags, char * data)
* If we have an unprocessed orphan list hanging
* around from a previously readonly bdev mount,
- * require a full umount/remount for now.
+ * require a full umount & mount for now.
if (es->s_last_orphan) {
ext3_msg(sb, KERN_WARNING, "warning: couldn't "
"remount RDWR because of unprocessed "
"orphan inode list. Please "
- "umount/remount instead.");
+ "umount & mount instead.");
err = -EINVAL;
goto restore_opts;