<div class="moz-text-flowed" style="font-family: -moz-fixed">(Please
don't top-post.)
On 12/20/08 18:18, Bhasker C V wrote:
Hi,
hdparm -r1 /dev/sda
works and I get this output when I read back the information with
plain '-r'
$ sudo hdparm -r /dev/sda
/dev/sda:
readonly = 1 (on)
Does this make it really read-only ?
That's what happens on my Firewire/SATA hard drive.
# hdparm -r1 /dev/sdc1
/dev/sdc1:
setting readonly to 1 (on)
readonly = 1 (on)
# mount -v /data/02
mount: block device /dev/sdc1 is write-protected, mounting read-only
/dev/sdc1 on /data/02 type ext3 (ro)
# dd count=10 if=/dev/hda1 of=/data/02/foo.bar
dd: opening `/data/02/foo.bar': Read-only file system
My harddisk is having a PV and then a VG ... LV which if i mount,
still is able to write to it ? [ VG activation is successful ]
(dont know if 'write' means really write a large file but I checked
using touch command and I am still able to create the file)
My kernel is 2.6.21.1
Is there anything I am missing here ?
Since you've got so many layers logicalness between the app and the
spindles, maybe you aren't really writing to the spindle you think you
are writing to? Or LVM is setting the read flag?