From: Ian Stirling <ian.stirling@mauve.plus.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Avinash Ramanath <avinashr@gmail.com>,
kernelnewbies@nl.linux.org, linux-kernel@vger.kernel.org
Subject: Re: Zeroing data blocks
Date: Sat, 05 Aug 2006 21:30:42 +0100 [thread overview]
Message-ID: <44D4FFF2.6040105@mauve.plus.com> (raw)
In-Reply-To: <1154799834.3054.93.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> On Sat, 2006-08-05 at 10:13 -0700, Avinash Ramanath wrote:
>
>>Hi,
>>
>>I want to do this at the filesystem-level not in user-space.
>>I have a stackable-filesystem that runs as a layer on top of the
>>existing filesystem (with all the function pointers mapped to the
>>corresponding base filesystem function pointers, and other suitable
>>adjustments).
>>So yes I have access to the filesystem.
>>But the question is how can I access those particular data-blocks?
>
>
> I think you misunderstood: You need to do this in the filesystem layer
> that allocates and tracks the blocks. You really can't do it outside
> that...
On modern (>200 meg or so) disk drives, you can't do it at all without
drive-specific debug tools.
The problem is that the drive, if it detects a bad sector, may well
remap the track that the sector is on to a spare track. You then
simply cannot access the old track. The drive may or may not zero
it for you.
Any standard access will simply ignore the old copy of the track.
It may or may not be possible to retrieve/erase it with disk-drive
specific tools that the vendor won't give you anyway.
If you want to do this reliably - you need to encrypt the disk
(not with loopcrypt or dm-crypt in its current state) so you can
just throw it away.
next prev parent reply other threads:[~2006-08-05 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <abcd72470607081856i47f15dedre9be9278ffa9bab4@mail.gmail.com>
[not found] ` <1152435182.3255.39.camel@laptopd505.fenrus.org>
2006-08-05 7:55 ` Zeroing data blocks Avinash Ramanath
2006-08-05 15:10 ` Arjan van de Ven
2006-08-05 17:13 ` Avinash Ramanath
2006-08-05 17:42 ` Arjan van de Ven
2006-08-05 20:30 ` Ian Stirling [this message]
2006-07-09 1:19 Avinash Ramanath
2006-07-09 18:55 ` Dave Boutcher
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=44D4FFF2.6040105@mauve.plus.com \
--to=ian.stirling@mauve.plus.com \
--cc=arjan@infradead.org \
--cc=avinashr@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--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