From: "Stephen C. Tweedie" <sct@redhat.com>
To: Mike Castle <dalgoda@ix.netcom.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.15-pre6 / EXT3 / ls shows '.journal' on root-fs.
Date: Thu, 22 Nov 2001 20:41:02 +0000 [thread overview]
Message-ID: <20011122204102.E11821@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0111192340500.4079-100000@imladris.surriel.com> <Pine.LNX.4.33.0111200344080.1395-100000@behemoth.ts.ray.fi> <20011119194354.A10322@thune.mrc-home.com> <E1661rR-0001Vl-00@localhost> <20011119200503.B10322@thune.mrc-home.com>
In-Reply-To: <20011119200503.B10322@thune.mrc-home.com>; from dalgoda@ix.netcom.com on Mon, Nov 19, 2001 at 08:05:03PM -0800
Hi,
On Mon, Nov 19, 2001 at 08:05:03PM -0800, Mike Castle wrote:
> Dump does not reliably work with live file systems with 2.4.x
It doesn't work reliably on live filesystems on ANY kernel. That
property is enhanced a bit by 2.4, that's all. There's no way that a
block-level dump can do things like walk file indirect chains
atomically on a live filesystem, even with 2.2.
Cheers,
Stephen
next prev parent reply other threads:[~2001-11-22 20:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-19 23:43 Kernel 2.4.15-pre6 / EXT3 / ls shows '.journal' on root-fs Patrick Mau
2001-11-19 23:55 ` Ryan Cumming
2001-11-20 1:20 ` Tommi Kyntola
2001-11-20 1:28 ` Ryan Cumming
2001-11-20 1:37 ` Tommi Kyntola
2001-11-20 1:41 ` Rik van Riel
2001-11-20 1:48 ` Tommi Kyntola
2001-11-20 3:43 ` Mike Castle
2001-11-20 3:46 ` Ryan Cumming
2001-11-20 4:05 ` Mike Castle
2001-11-20 4:14 ` Ryan Cumming
2001-11-22 20:41 ` Stephen C. Tweedie [this message]
2001-11-20 1:55 ` Ryan Cumming
2001-11-20 19:19 ` Andreas Dilger
2001-11-22 8:48 ` Allan Sandfeld
2001-11-23 19:49 ` Mike Fedyk
2001-11-22 20:39 ` Stephen C. Tweedie
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=20011122204102.E11821@redhat.com \
--to=sct@redhat.com \
--cc=dalgoda@ix.netcom.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.