From: Jan Kara <jack@suse.cz>
To: Bas van Schaik <bas@tuxes.nl>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Used dd to copy an ext4 filesystem, but target contained an old (mounted!) filesystem
Date: Tue, 18 Oct 2011 03:06:39 +0200 [thread overview]
Message-ID: <20111018010639.GJ4528@quack.suse.cz> (raw)
In-Reply-To: <4E9C1704.5000304@tuxes.nl>
Hi,
On Mon 17-10-11 12:52:36, Bas van Schaik wrote:
> Long story short: I dd'ed 1.5TB of data to an LVM volume 'newdata'
> that already contained a filesystem (which I wanted to get rid of).
> Unfortunately, the old filesystem turned out to be mounted during
> the dd. After noticing this, I quickly created LVM snapshots of the
> 'newdata' volume before unmounting the old filesystem (hoping that
> it didn't write out it fs data structures to 'newdata' yet, as I
> didn't access it) and tried mounting the snapshot. Unfortunately, it
> showed the old directory listing.
So let me check I understand what happened. You had some "sourcevol"
containing a filesystem and 1.5 TB of data. You did:
dd if=sourcevol of=newdata
Now you noticed newdata was mounted so you created lvm snapshot of newdata.
Then umount newdata.
Now if you mount newdata you still see contents of "sourcevol" but you'd
like to see "newdata". Am I correct?
If that's the case, shouldn't you try to mount the snapshot volume instead
of simply "newdata"?
> The actual data is definitely sitting on the 'newdata' volume, but
> the filesystem datastructures simply don't know about it. The source
> of the data is definitely gone, I can't simply dd it again.
>
> Is there any other location where ext4 stores a copy of its data
> structures?
Not really. Only the superblock is duplicated.
> Or any other tips & tricks?
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2011-10-18 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 11:52 Used dd to copy an ext4 filesystem, but target contained an old (mounted!) filesystem Bas van Schaik
2011-10-17 12:37 ` Bas van Schaik
2011-10-18 1:06 ` Jan Kara [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=20111018010639.GJ4528@quack.suse.cz \
--to=jack@suse.cz \
--cc=bas@tuxes.nl \
--cc=linux-ext4@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).