From mboxrd@z Thu Jan  1 00:00:00 1970
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
Date: Thu, 30 Dec 2010 01:06:13 +0700
Subject: Blocking the access to the device files.
In-Reply-To: <AANLkTik1-wa=oa29Dv_Eh8iOzmau02ih-Vr_ObhTbK+N@mail.gmail.com>
References: <AANLkTi=rBO9cYXNLXCg0dursye8tTq=BpgHjpSdRU37J@mail.gmail.com>
	<AANLkTinFb=eB=rUWO+ng2CYq7ips9HL3POXFcVHNchC3@mail.gmail.com>
	<AANLkTik1-wa=oa29Dv_Eh8iOzmau02ih-Vr_ObhTbK+N@mail.gmail.com>
Message-ID: <AANLkTimE3rS_a3T1Mo1pSn9agEGbWyE_CPtqe0CHwxAb@mail.gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

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