- 1. can't mount XFS from a read-only device (score: 1)
- Author: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
- Date: Fri, 9 Oct 2009 17:09:37 +0200
- Hello all, I'm using a RAID enclosure that provides read-only snapshots. It works perfectly fine using JFS. But with XFS, I keep trying and it keeps failing : XFS mounting filesystem sdb Ending clean
- /archives/xfs/2009-10/msg00080.html (7,295 bytes)
- 2. Re: can't mount XFS from a read-only device (score: 1)
- Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
- Date: Fri, 09 Oct 2009 13:59:13 -0500
- try mount -o norecovery (and maybe -o nobarrier) -Eric
- /archives/xfs/2009-10/msg00081.html (9,560 bytes)
- 3. Re: can't mount XFS from a read-only device (score: 1)
- Author: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
- Date: Fri, 9 Oct 2009 21:19:31 +0200
- Le Fri, 9 Oct 2009 19:43:51 +0200 vous écriviez: Yes, norecovery did it. I did snapshots previously using LVM, but these are writable, so only "nouuid" is necessary (to mount the original FS and snap
- /archives/xfs/2009-10/msg00082.html (8,452 bytes)
- 4. Re: can't mount XFS from a read-only device (score: 1)
- Author: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
- Date: Fri, 9 Oct 2009 21:21:50 +0200
- Le Fri, 09 Oct 2009 13:59:13 -0500 vous écriviez: Thank you, that worked. I can't help but think that when given the "ro" option, XFS shouldn't try to write a single bit to the underlying device, or
- /archives/xfs/2009-10/msg00083.html (8,247 bytes)
- 5. Re: can't mount XFS from a read-only device (score: 1)
- Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
- Date: Fri, 09 Oct 2009 14:28:47 -0500
- For a dirty log, we do still recover -unless- the underlying device is RO. Otherwise you get a corrupt fs mounted ro.... other filesystems do the same thing, FWIW. For a clean log I agree; what kerne
- /archives/xfs/2009-10/msg00084.html (8,695 bytes)
- 6. Re: can't mount XFS from a read-only device (score: 1)
- Author: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
- Date: Fri, 9 Oct 2009 21:50:27 +0200
- Le Fri, 09 Oct 2009 14:28:47 -0500 vous écriviez: It's a 2.6.24.7. I did a quick try with 2.6.27.25 and got exactly the same error. Yes, norecovery was the missing part. -- -- Emmanuel Florac www.int
- /archives/xfs/2009-10/msg00085.html (8,389 bytes)
This search system is powered by
Namazu