From: David Wilk <davidwilk@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: data retention after mkfs.ext3
Date: Wed, 8 Feb 2006 15:05:19 -0700 [thread overview]
Message-ID: <a4403ff60602081405r716d9026r67ddd9d744cdabdb@mail.gmail.com> (raw)
We deploy a linux system by rsync'ing a filesystem off of a squashfs
FS on a CD. The deployment is automated and always involves an
mkfs.ext3 prior to any file copy. We have had some reports that tend
to indicate that some of the data from a previous install (of the same
method) is corrupting at least some of the files on a new install.
Old settings and random behavior has been seen, and breaking the RAID1
logical drive and rebuilding prior to install has always fixed the
issue.
It is my impression that mkfs.ext3 will make any existing data on a
block device invisiable to the new ext3 FS. Is it possible that if
the old FS is similar enough to the new one that the old data could
somehow influence the new files written to a new ext3 FS?
I know this *should* be impossible, but is it truly impossible?
reply other threads:[~2006-02-08 22:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a4403ff60602081405r716d9026r67ddd9d744cdabdb@mail.gmail.com \
--to=davidwilk@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®