From: "Janos Haar" <janos.haar@netcenter.hu>
To: "Milton Miller" <miltonm@bga.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: How can i read really 512 byte?
Date: Wed, 1 Oct 2008 12:23:32 +0200 [thread overview]
Message-ID: <409101c923af$c8092020$0400a8c0@dcccs> (raw)
In-Reply-To: 200809301450.m8UEo5wT027331@sullivan.realtime.net
----- Original Message -----
From: "Milton Miller" <miltonm@bga.com>
To: "Janos Haar" <janos.haar@netcenter.hu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Tuesday, September 30, 2008 4:50 PM
Subject: How can i read really 512 byte?
> On Tue, 30 Sep 2008 at 08:29:15 -0400 (EDT), Janos Haar wrote:
>> Now i am working on recover some data from one defective drive. I
>> am using dd_rescue, and dd, but both ready only 4K, i think, because
>> the kernel's block size is 4K.
>>
>> I have tried to google for the solution, but only found this trick:
>>
>> losetup /dev/loop0 /dev/hdc
>> blockdev --setbsz 512 /dev/hdc
>>
>> and after this set, trying to read the hdc...
>>
>> It looks like working on the first look, but not really. :-( The
>> 512 size bad sectors still have 4K sizes, but the reading attempt
>> takes more (8x ?) longer.
>>
>> Somebody can help me to set the reading block size to 512 byte?
>
> You need to add O_DIRECT to the open call in the flags parameter
> (the second argument). (My brother tested this a year or so ago,
> and it worked for him).
>
> milton
Hello,
Thank you for the information.
Can you help me a little bit more?
Where need to add this parameter?
In the kernel, in the blocked's source, or in the dd_rescue's source?
Thanks,
Janos Haar
next prev parent reply other threads:[~2008-10-01 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 12:25 How can i read really 512 byte? Janos Haar
2008-09-30 14:50 ` Milton Miller
2008-10-01 10:23 ` Janos Haar [this message]
2008-10-01 12:22 ` Milton Miller
2008-10-01 12:36 ` Andrey Borzenkov
2008-10-01 13:44 ` Janos Haar
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='409101c923af$c8092020$0400a8c0@dcccs' \
--to=janos.haar@netcenter.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=miltonm@bga.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.