This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] fsck.reiserfs problem

To: "Paul Larson" <pl@xxxxxxxxxx>, "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] fsck.reiserfs problem
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Thu, 17 Mar 2005 20:51:00 -0000
Cc: <ian.pratt@xxxxxxxxxxxx>
Delivery-date: Thu, 17 Mar 2005 20:52:28 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Thread-index: AcUrJ/RhVX2XOi/zTguY4gCHUQvH7gACn15g
Thread-topic: [Xen-devel] fsck.reiserfs problem
> Anyone seen this before? from fsck.reiserfs on boot under xenU
> 2.0-testing latest bk:
> get_dma_info failed Bad file descriptor
> ###########
> reiserfsck --check started at Thu Mar 17 12:32:18 2005
> ###########
> Replaying journal..
> Reiserfs journal '/dev/hda2' in blocks [18..8211]: 0 transactions
> replayed
> bwrite: write 4096 bytes returned -1 (block=16, dev=3): Operation not
> permitted
> It's happening at boot time on my /usr which is read-only.  
> I'm guessing
> that's the problem based on the output, but how do people 
> normally work
> around this when they try to reuse their /usr as read-only?  It's
> preventing me from booting normally.

The file system is currently not in a clean state. If you fsck it from
dom0 and then make sure you only ever mount it read-only in dom0, you
should be able to get it back to a clean state, and then it should work
OK bexing exported read-only to other domains.


SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>