From: Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com>
Subject: Re: [PATCH] ext4: fix message in ext4_remount for rw-remount case
Date: Mon, 08 Aug 2011 19:20:58 +0900
Message-ID: <4E3FB88A.7000305@jp.fujitsu.com>
References: <20110801135628.3257a561.toshi.okajima@jp.fujitsu.com> <j1k60i$481$1@dough.gmane.org>
Reply-To: toshi.okajima@jp.fujitsu.com
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: linux-ext4@vger.kernel.org
To: Sergei Zhirikov <sfzhi@yahoo.com>
In-Reply-To: <j1k60i$481$1@dough.gmane.org>
Sender: linux-ext4-owner@vger.kernel.org

Hi.

(2011/08/07 4:51), Sergei Zhirikov wrote:
> On 2011-08-01 06:56, 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.
> On 2011-08-01 06:56, Toshiyuki Okajima wrote:
>
> Hi,
>
> I have just encountered this feature and I have a question:
>

> How do I umount/mount if it's my root filesystem?
> Is there anything I can do besides "the Microsoft way" (reboot)?
Only way that you can recover this situation by is to reboot
because the root filesystem cannot umount.

Best Regards,
Toshiyuki Okajima