From: Toshiyuki Okajima Date: Tue, 2 Aug 2011 09:16:57 +0000 (+0900) Subject: ext3: fix message in ext3_remount for rw-remount case X-Git-Tag: v3.2-rc1~86^2~18 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=1cde201da4e97f10a5dd2434cff4ceff381603d1;p=profile%2Fivi%2Fkernel-x86-ivi.git 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 Signed-off-by: Jan Kara --- diff --git a/fs/ext3/super.c b/fs/ext3/super.c index 7beb69a..2043bcc 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; }