From: Eric Sandeen <sandeen@redhat.com>
To: 7eggert@gmx.de
Cc: Eric Sandeen <sandeen@sandeen.net>,
Valdis.Kletnieks@vt.edu,
Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
t-sato@yk.jp.nec.com
Subject: Re: [PATCH] Allow SysRq emergency sync to thaw frozen filesystems
Date: Sat, 17 Jan 2009 09:44:14 -0600 [thread overview]
Message-ID: <4971FCCE.3020005@redhat.com> (raw)
In-Reply-To: <E1LOBlz-0001tI-Oo@be1.7eggert.dyndns.org>
Bodo Eggert wrote:
> Eric Sandeen <sandeen@sandeen.net> wrote:
>> Valdis.Kletnieks@vt.edu wrote:
>>> On Thu, 15 Jan 2009 21:59:10 CST, Eric Sandeen said:
>
>>>> Oh, actually, I'd think not. If the freeze was done properly by the
>>>> filesystem, all data was flushed, the fs was quiesced, and new IO was
>>>> blocked. pdflush should never be visiting these...
>>> Yes, but a lot of 'if's - and usually you're reaching for sysrq-S precisely
>>> *because* you suspect that stuff wasn't happening properly on its own...
>> Actually, only one if - if the fs implemented freeze properly.
>>
>> Well, the use case I envision here is something like:
>>
>> # freeze /my/mount/point/to/fs/to/snapshot
>>
>> except oops, that wasn't mounted, and you just froze your root fs.
>
> Maybe freeze should protect against that by requiring to specify the exact
> mountpount, unless you say freeze --subdir?
That's a good idea. My "freeze" above was a hypothetical tool which
doesn't really exist yet, but should get that enhancement. :)
(xfs_freeze does not do this checking today, it probably should)
-Eric
next prev parent reply other threads:[~2009-01-17 15:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bUrIs-Za-3@gated-at.bofh.it>
[not found] ` <bUKL7-6vo-3@gated-at.bofh.it>
[not found] ` <bUNSJ-2Vn-13@gated-at.bofh.it>
[not found] ` <bUO2t-376-5@gated-at.bofh.it>
[not found] ` <bUYXL-3Qb-25@gated-at.bofh.it>
[not found] ` <bUZ7p-448-9@gated-at.bofh.it>
2009-01-17 14:03 ` [PATCH] Allow SysRq emergency sync to thaw frozen filesystems Bodo Eggert
2009-01-17 15:44 ` Eric Sandeen [this message]
2009-01-15 4:06 Eric Sandeen
2009-01-16 0:20 ` Andrew Morton
2009-01-16 3:49 ` Eric Sandeen
2009-01-16 3:59 ` Eric Sandeen
2009-01-16 15:33 ` Valdis.Kletnieks
2009-01-16 15:40 ` Eric Sandeen
2009-01-16 16:21 ` Dave Kleikamp
2009-01-16 16:42 ` Dave Kleikamp
2009-01-16 8:48 ` Pavel Machek
2009-01-16 15:17 ` Valdis.Kletnieks
2009-01-16 15:28 ` Eric Sandeen
2009-01-16 15:33 ` Pavel Machek
2009-01-16 15:40 ` Theodore Tso
2009-01-16 15:52 ` Valdis.Kletnieks
2009-01-16 16:08 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4971FCCE.3020005@redhat.com \
--to=sandeen@redhat.com \
--cc=7eggert@gmx.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=t-sato@yk.jp.nec.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox