I was bitten by this bug too (very strange, the kernel reported the FS as read-write, and touch and rm would work , but chmod gave 'read only filesystem'). Getting rid of XFS flags in /etc/fstab was a workaround for me too.
The people on #xfs freenode helped me out here, and they noted that, apart from this patch, ubuntu intrepid is also missing a very important data corruption fix for XFS.
<hch> and http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=co mmitdiff;h=73f6aa4d44ab6157badc456ddfa05b31e58de5f0 while you're at
it
<hch> without the latter one you can get really bad corruption if you rely on
barriers
<hch> looks like not many people use xfs on ubuntu..
(...)
<hch> but the barrier fix would be extremely useful too
<hch> otherwise we'll get lots of complaints from ubuntu users about data corruption
Hello,
I was bitten by this bug too (very strange, the kernel reported the FS as read-write, and touch and rm would work , but chmod gave 'read only filesystem'). Getting rid of XFS flags in /etc/fstab was a workaround for me too.
The people on #xfs freenode helped me out here, and they noted that, apart from this patch, ubuntu intrepid is also missing a very important data corruption fix for XFS.
<hch> and git.kernel. org/?p= linux/kernel/ git/torvalds/ linux-2. 6.git;a= co
mmitdiff; h=73f6aa4d44ab6 157badc456ddfa0 5b31e58de5f0 while you're at
http://
it
<hch> without the latter one you can get really bad corruption if you rely on
barriers
<hch> looks like not many people use xfs on ubuntu..
(...)
<hch> but the barrier fix would be extremely useful too
corruption
<hch> otherwise we'll get lots of complaints from ubuntu users about data
should i log a separate bugreport about this ?
thanks!
greetings,
Frank