-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 05 Apr 2012 21:10:07 -0400 Phillip Susi <psusi@xxxxxxxxxx> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 04/05/2012 07:24 PM, NeilBrown wrote:
> > Something wrote to the md device despite it being marked 'read-only'.
> > Some filesystems do that to replay their journal. totally inexcusable
> > behaviour, but what can we do....
>
> I agree... read-only means read ONLY.
>
> > I'm surprised that would happen during installation though.
> > But certainly the array is marked read-only, and certainly something is
> > writing to it, and that is the real bug.
>
> If the block device is flagged as read only, then shouldn't it reject write attempts even if the fs or userspace issue them?
>
It will reject writes from user-space, and it will reject attempts to mount a
filesystem unless the filesystem is mounted "read-only".
But if a read-only mounted filesystem decides to write anyway (XFS, ext3,
ext4...) then the block layer doesn't stop it.
NeilBrown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iQIVAwUBT4N0Ijnsnt1WYoG5AQI4DQ/9HF2EJMx2RLV8pAb6pOCY4YRcjGPomRpe
86MxPF0GtlFI+ZPZP7fIHmGxkDYg6Y3zW/sNDAXS7xHzt3gyHa9w91adv54BK79T
xQghdL+ZXS3NxdHWi04Ya20R44VGnVKuoyNdP8mgddZi4ABoy3eaQSUdM9uoJ/bn
79JKPlUfbwTSSx0ub20ZINZU/KjIBxxyyp5bT3RxNqw795G6XIx6jpHMgQNomMSL
TpywEky2gGjnC/6T8mM80EGKv+Fx8IMteWb7StIuMu0xNPyfrwkUGVKHAFs7PbAT
CTkV/vqkNO/DHeDiXSmepH5tQAV0BsNUFRo4DzFW5id0ANaSFCj0wPXQjPAkfkOl
XVBxVFm8riVQtXYYAjFqj4aAUkkovp3bpCwPgy5HajmxBkTOAt9dRyy1Uzp5VRNh
y942F4xi6uiTG0H3NmZaY7nvDVYkLVAn6wMrzm4UAbgxmvIeIgKU773FEt0A1HRy
oXE+gVLT/V2pF1+S0X5s3lp6cDpUbd5M8hCsN9rhmWovPV6mEwfWk857+eVvmiRX
lUxgC56HumMf0vvTsmJOS5GOgnHxADV7ugDYIdau4wpulghL/pgt6wOrCYBtzbA1
moqaD0BSlQBBwXRL/j8qdH3dm5ResNxnQpPURYU7aZX5T0mQ6bQ1stjXZ9qOmw3A
zhSC8abbZpk=
=HgL3
-----END PGP SIGNATURE-----
ÿôèº{.nÇ+?·?®??+%?Ëÿ±éݶ¥?wÿº{.nÇ+?·¥?{±þ¶¢wø§¶?¡Ü¨}©?²Æ zÚ&j:+v?¨þø ¯ù ®w¥þ?à2?Þ?¨èÚ&¢)ß¡«a¶Úÿÿûàz¿äz¹Þ?ú+?ù???Ý¢jÿ?wèþf
