[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: no file system for xbd0 (dev 0x8e00)
Le 30/05/13 16:16, Emile `iMil' Heitor a écrit :
I suggest checking this from a dom0 perspective first before
continuing the hunt for weird and uncommon file system corruption
issues in the domU.
In the dom0, make sure your lvm is active, e.g. marked with an 'a'
rather than a 'd'
in the output of lvm lvs. I suspect you couldn't even get a disklabel
if it wasn't, but it can't hurt to check the lvm status in dom0 anyway.
I'd also suggest in dom0 dd'ing the lvm's raw device to /dev/null to
make sure there are no i/o errors.
lvs output, from the dom0, seems ok:
webserver vg1 owi-ao 20.00g
The `o'rigin attribute is set because I've just done a snapshot just in
dd from the vbd to /dev/null went well also.
I have a bad feeling about this...
Do you get the same output between "disklabel /dev/xbd1" and "disklabel
I would also try dd'ing the LV and pass it through vnconfig(8) (never
did it, YMMV).
I've seen weird behavior from domU when it falls on specific forbidden
operations from dom0's backend (like trying to overwrite the disk's
disklabel after a silent corruption).
Main Index |
Thread Index |