All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: Yakov Lerner <iler.ml@gmail.com>
Cc: Kernel <linux-kernel@vger.kernel.org>
Subject: Re: locking sectors of raw disk (raw read-write test of mounted disk)
Date: Thu, 16 Nov 2006 10:28:04 -0500	[thread overview]
Message-ID: <455C8384.1000907@cfl.rr.com> (raw)
In-Reply-To: <f36b08ee0611160215i7dcbd27p76963cb12d0bc12f@mail.gmail.com>

Yakov Lerner wrote:
> I don't want to tamper wuith data. I want to raw write back exacty
> same raw data that I read in. I only want to make sure that kernel
> doesn't write modified data between in between my read-write pair.

Ahh, in that case you might be able to do this using the device mapper. 
  You could keep the filesystem mounted on the device mapper with a 
mapping to the underlying disk device.  Then change that mapping on the 
fly to mark a section of the device as mapped to a ramdisk and copy ( 
while that section is suspended ) the original data there.  Then resume 
the section, tamper with the underlying disk, then suspend the ramdisk 
mapping, copy it back to the underlying disk, then change the mapping 
back to normal.  You might also use a snapshot dm target instead of a 
ramdisk.



      reply	other threads:[~2006-11-16 15:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 20:06 locking sectors of raw disk (raw read-write test of mounted disk) Yakov Lerner
2006-11-15 21:41 ` Phillip Susi
2006-11-15 22:03   ` linux-os (Dick Johnson)
2006-11-16 10:15   ` Yakov Lerner
2006-11-16 15:28     ` Phillip Susi [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=455C8384.1000907@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=iler.ml@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 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.