Comment 13 for bug 273601

Leann, thanks for the reply on my bug that's a dup of this. I thought I'd already posted my workaround, but it turns out I only posted it on bug 253786 (/dev/.static/dev is left read-only). Since I found a workaround, this bug hasn't caused me any problems.

Anyway, you can convince the init scripts to remount the bind mount read-write as well as the main root filesystem with this in fstab
/dev /dev/.static/dev bind remount,rw 0 0

 That avoids triggering the bug with XFS root filesystems. And it makes /dev/.static/dev read-write, so MAKEDEV works, so I'll be keeping this in my fstab even after the XFS bug is fixed. see bug 253786 for more discussion on ro/rw, and how it gets that way in the first place.

 If you don't want to break the kernel freeze, you could possibly add this workaround to update-manager's collection of quirks. (e.g. test if xfs_info / shows that the root filesystem is xfs, then append a line to /etc/fstab.)

 Hmm, reading the fix description, XFS has a per-FS read-only flag? That doesn't sound like it would interact well with various combinations of read-only and read-write bind mounts... Could be a security hole if you think you have a ro bind mount for a chroot, but some FS ops are allowed. I'll test this and report a bug if I remember and have time, and it's not already known.