| To: | "David Chinner" <dgc@xxxxxxx> |
|---|---|
| Subject: | Re: [RFC PATCH 2/2] Add timeout feature |
| From: | "Takashi Sato" <t-sato@xxxxxxxxxxxxx> |
| Date: | Wed, 2 Apr 2008 21:16:59 +0900 |
| Cc: | <linux-kernel@xxxxxxxxxxxxxxx>, <dm-devel@xxxxxxxxxx>, <xfs@xxxxxxxxxxx>, <linux-fsdevel@xxxxxxxxxxxxxxx>, <linux-ext4@xxxxxxxxxxxxxxx> |
| In-reply-to: | <20080402062147.GH103491721@xxxxxxx> |
| References: | <20080328180736t-sato@xxxxxxxxxxxxxxx> <20080331000057.GI108924158@xxxxxxx> <2530BB4B166747659C8F65C9C3DE7CFB@xxxxxxxxxxxxxxxx> <20080402062147.GH103491721@xxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
Hi, David Chinner wrote: Exactly my timeout feature is only for an application, not for freeze_bdev(). I think it is needed for the situation we can't unfreeze from userspace. (e.g. Freezing the root filesystem)Ummm - why can't you unfreeze the root fs from userspace? freezing only prevents modification to the filesystem. A frozen filesystem is effectively a read-only filesystem... On XFS: # xfs_freeze -f / # echo $? 0 # xfs_freeze -u / # echo $? 0 Yes. If we have already logged in, we can unfreeze as above. But if not, we cannot log in and unfreeze because the modification of /var/log/wtmp is blocked in the log-in procedure. The timeout feature will work in such case. Cheers, Takashi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Serious XFS crash, Emmanuel Florac |
|---|---|
| Next by Date: | Re: Serious XFS crash, David Chinner |
| Previous by Thread: | Re: [RFC PATCH 2/2] Add timeout feature, David Chinner |
| Next by Thread: | Re: Serious XFS crash, Emmanuel Florac |
| Indexes: | [Date] [Thread] [Top] [All Lists] |