From: "Jim C. Brown" <jbrown106@phreaker.net>
To: "Kirkwood, David A" <DAVID.A.KIRKWOOD@saic.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: dump on ext3
Date: Thu, 6 Jan 2005 16:55:47 -0500 [thread overview]
Message-ID: <20050106215547.GA21519@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <D08E09E5E39ED311B01E00C00D0142FF06CE7252@US-ARL-TRG.mail.saic.com>
On Thu, Jan 06, 2005 at 04:13:16PM -0500, Kirkwood, David A wrote:
> Does dump work reliably on an ext3 filesystem?
>
> Here's the senario:
>
> I have a raid 5 linux system ( RH 7.3 ). I currently backup the system to
> tape in case of catastrophic failure. I am up to multitape backups for full
> user partitions.I want to use incremental dumps and spread my full system
> dumps further apart, but tme man page says dump can be used for ext2. There
> is no mention of ext3 one way or the other. Assuming 1 tape drive, the need
> to do backups unattended, the inability to shut the system down
> everttime I need to dump files, I need to use dump unless someone has a
> better solution. New backup h/w etc in not an option as i have already
> submitted need for tape library etc and its working its way through the
> corporate higharchy but it may be 6 month untill I see something.
>
> As always, all input is appreciated.
>
> Dave
I'm not 100% certain of this, but it should work. File system wise, ext3
is just ext2 with a journal inode (which looks like a regular ext2 file).
I suppose it is possible that dump might have a problem with the journal inode
on a mounted ext3 system, but even if that is the case it should be easy to work
around, as it seems Dump 0.4b36 from http://sourceforge.net/projects/dump/
supports ext3 (all versions do, but that's the only one called ext2/ext3 dump).
You might also be interested to read this, from
http://nslug.ns.ca/pipermail/nslug/2003-November/005980.html
> Changes between versions 0.4b9 and 0.4b10 (released November 21, 1999)
> ======================================================================
> ...
> 4. Integrate a patch from Jeremy Fitzhardinge <jeremy at goop.org>
> which allows dump on an active ext3 filesystem. However, this
> is a "quick and dirty" patch which enables backup of an ext3
> filesystem through the ext2 compatibility (by ignoring the
> NEEDS_RECOVERY bit). The journal file is not recognized and
> it is dumped (it should not).
>
>
> Unless I have missed something, nobody ever saw a need to improve on the
> "quick and dirty" patch (or at least there is no subsequent mention of ext3
> in the changelog) so it should be possible with a modern 'dump' to dump ext3
> and get exactly the same results as if the filesystem had been ext2, just as
> it says above.
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
prev parent reply other threads:[~2005-01-06 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 21:13 dump on ext3 Kirkwood, David A
2005-01-06 21:55 ` Jim C. Brown [this message]
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=20050106215547.GA21519@jbrown.mylinuxbox.org \
--to=jbrown106@phreaker.net \
--cc=DAVID.A.KIRKWOOD@saic.com \
--cc=linux-admin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).