[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E3675D6.3010201@jp.fujitsu.com>
Date: Mon, 01 Aug 2011 18:45:58 +0900
From: Toshiyuki Okajima <toshi.okajima@...fujitsu.com>
To: Jan Kara <jack@...e.cz>
CC: akpm@...ux-foundation.org, adilger.kernel@...ger.ca,
linux-ext4@...r.kernel.org
Subject: Re: [PATCH] ext3: fix message in ext3_remount for rw-remount case
Hi.
(2011/08/01 17:45), Jan Kara wrote:
> On Mon 01-08-11 13:54:51, Toshiyuki Okajima wrote:
>> If there are some inodes in orphan list while a filesystem is being
>> read-only mounted, we should recommend that pepole umount and then
>> mount it when they try to remount with read-write. But the current
>> message/comment recommends that they umount and then remount it.
>>
>> ext3_remount:
>> /*
>> * If we have an unprocessed orphan list hanging
>> * around from a previously readonly bdev mount,
>> * require a full umount/remount for now.
>> ^^^^^^^^^^^^^^
>> */
>> if (es->s_last_orphan) {
>> printk(KERN_WARNING "EXT3-fs: %s: couldn't "
>> "remount RDWR because of unprocessed "
>> "orphan inode list. Please "
>> "umount/remount instead.\n",
>> ^^^^^^^^^^^^^^
>> sb->s_id);
> OK, so how about using "umount& mount"? The '/' is what would confuse me
OK. I modify it like your comment.
umount/mount => umount & mount
> the most... BTW, I guess you didn't really see this message in practice, did
> you?
No.
I have seen this message in practice while quotacheck command was repeatedly
executed per an hour.
Thanks,
Toshiyuki Okajima
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists