From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Blocking the access to the device files.
Date: Thu, 30 Dec 2010 01:06:13 +0700 [thread overview]
Message-ID: <AANLkTimE3rS_a3T1Mo1pSn9agEGbWyE_CPtqe0CHwxAb@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik1-wa=oa29Dv_Eh8iOzmau02ih-Vr_ObhTbK+N@mail.gmail.com>
Hi Greg :)
On Thu, Dec 30, 2010 at 00:01, Greg Freemyer <greg.freemyer@gmail.com> wrote:
> My guess is that it is more complex than that.
>
> Some filesystems have issues if the raw drive is read while the
> filesystem is mounted. ?I think it is caused by inconsistencies in the
> various cache's. ?ie. iirc, At least in the 2.4 kernel there was not a
> single unified cache for block layer and filesystems. ?So doing raw
> reads of underlying device while it was mounted could cause the caches
> to get out of sync.
Oh, that issue? well, in that case, I have no prevent such thing...I
was offering the previous idea since I have very little cues on what
Prasad mean by "disabling access"....
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2010-12-29 18:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 13:06 Blocking the access to the device files Prasad Joshi
2010-12-29 16:12 ` Mulyadi Santosa
2010-12-29 17:01 ` Greg Freemyer
2010-12-29 18:06 ` Mulyadi Santosa [this message]
2010-12-29 18:54 ` mindentropy
2010-12-29 19:00 ` Mulyadi Santosa
2010-12-29 19:02 ` Greg Freemyer
2010-12-29 19:07 ` Mulyadi Santosa
2010-12-29 19:09 ` Greg Freemyer
2010-12-29 23:32 ` Prasad Joshi
2010-12-30 0:07 ` Greg Freemyer
2010-12-30 0:24 ` Henry Gebhardt
2010-12-30 7:10 ` Rajat Sharma
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=AANLkTimE3rS_a3T1Mo1pSn9agEGbWyE_CPtqe0CHwxAb@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).