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: Wed, 15 Nov 2006 16:41:13 -0500	[thread overview]
Message-ID: <455B8979.6090101@cfl.rr.com> (raw)
In-Reply-To: <f36b08ee0611151206k50284ef9n43d7edf744ae2f19@mail.gmail.com>

No, you can not tamper with the underlying data while the kernel has it 
mounted.

Yakov Lerner wrote:
> I'd like to make read-write test of the raw disk, and disk has
> mounted partitions. Is it possible to lock  range of sectors
> of the raw device so that any kernel code that wants to write
> to this range will sleep ? (so that test
>    { lock range; read /dev/hda->buf; write buf->/dev/hda; unlock }
> won't corrupt the filesysyem ?)
> 
> Thanks
> Yakov


  reply	other threads:[~2006-11-15 21:40 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 [this message]
2006-11-15 22:03   ` linux-os (Dick Johnson)
2006-11-16 10:15   ` Yakov Lerner
2006-11-16 15:28     ` Phillip Susi

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=455B8979.6090101@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.