From: Jesper Juhl <juhl@eisenstein.dk>
To: Klaus Dittrich <kladit@t-online.de>
Cc: linux-kernel@vger.kernel.org, klaus@df1tlb.local.here
Subject: Re: 2.4.10 and dd
Date: Wed, 26 Sep 2001 18:46:22 +0200 [thread overview]
Message-ID: <3BB2065E.B0BAE05F@eisenstein.dk> (raw)
In-Reply-To: <200109272002.WAA02203@df1tlb.local.here>
Klaus Dittrich wrote:
> I do my backup using dd if=/dev/sda of=/dev/sdb bs=1024k.
ehh, isn't that kind of dangerous???
What if files move around on disk while dd is running? imagine that dd is in the process of copying blocks belonging to a big file "foo",
and now in the middle of this something causes "foo" (or just parts of "foo") to move to a different location - you now have a seriously screwed
copy of "foo" on the new disk...
I'd expect that all sorts of strange corruption of the copy could happen that way. I could be wrong, and maybe someone who knows more about
how the filesystems work can tell if I am, but I know for sure that I would never dare to do backups that way.
Best regards,
Jesper Juhl
juhl@eisenstein.dk
prev parent reply other threads:[~2001-09-27 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 20:02 Klaus Dittrich
2001-09-26 16:46 ` Jesper Juhl [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=3BB2065E.B0BAE05F@eisenstein.dk \
--to=juhl@eisenstein.dk \
--cc=kladit@t-online.de \
--cc=klaus@df1tlb.local.here \
--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®