From: NeilBrown <neilb@suse.de>
To: Phillip Susi <psusi@ubuntu.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Intel fakeraid working?
Date: Tue, 10 Apr 2012 09:43:30 +1000 [thread overview]
Message-ID: <20120410094330.00fb2477@notabene.brown> (raw)
In-Reply-To: <4F7E426F.5000604@ubuntu.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 05 Apr 2012 21:10:07 -0400 Phillip Susi <psusi@ubuntu.com> 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-----
next prev parent reply other threads:[~2012-04-09 23:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 0:56 Intel fakeraid working? Phillip Susi
2012-04-05 1:13 ` NeilBrown
2012-04-05 18:20 ` Phillip Susi
2012-04-05 23:25 ` NeilBrown
2012-04-06 10:36 ` Jan Ceuleers
2012-04-05 18:23 ` Phillip Susi
2012-04-05 23:24 ` NeilBrown
2012-04-06 1:10 ` Phillip Susi
2012-04-09 23:43 ` NeilBrown [this message]
2012-04-10 13:14 ` Phillip Susi
2012-04-23 2:25 ` NeilBrown
2012-04-23 4:06 ` 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=20120410094330.00fb2477@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=psusi@ubuntu.com \
/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.