linux-ext4 - Re: [PATCH] ext4: fix message in ext4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 08 Aug 2011 19:20:58 +0900
From:	Toshiyuki Okajima <toshi.okajima@...fujitsu.com>
To:	Sergei Zhirikov <sfzhi@...oo.com>
CC:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH] ext4: fix message in ext4_remount for rw-remount case

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


--
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