From: Harald Dunkel <harald.dunkel@t-online.de>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: question about SATA vs (SATA via USB)
Date: Wed, 26 Dec 2007 21:35:01 +0100 [thread overview]
Message-ID: <4772BAF5.6090301@t-online.de> (raw)
In-Reply-To: <47721363.9050601@gmail.com>
Hi Tejun,
Tejun Heo wrote:
> Harri wrote:
>> Next I mounted (rw, shame on me) the old SATA disk via USB
>> to the PC, and tried to copy the data. But during the copy
>> there were some syslog messages about file system corruptions
>> on the old disk. I stopped rsync, unmounted the disk,
>> and ran fsck, but it was damaged beyond repair. No chance
>> to recover any data.
>
> Hmmm... interesting. That isn't supposed to happen. Do you have kernel
> logs saved?
>
Sorry, but the logs have been lost. The new 500 GB disk had
an I/O error and had to be replaced. I doubt that this I/O
error was the reason for corrupting the filesystem on the
other disk, but there is no way to be sure, afaics.
I would suggest to ignore this problem for now.
Regards
Harri
prev parent reply other threads:[~2007-12-26 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 8:57 question about SATA vs (SATA via USB) Harri
2007-12-26 8:40 ` Tejun Heo
2007-12-26 20:35 ` Harald Dunkel [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=4772BAF5.6090301@t-online.de \
--to=harald.dunkel@t-online.de \
--cc=htejun@gmail.com \
--cc=linux-ide@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).