<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: XEN disk file corrupt in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/xen-disk-file-corrupt/m-p/4341123#M34916</link>
    <description>Did you reduce the filesystem before you reduced the SAN volume? If you made the SAN volume smaller than the filesystem then you did corrupt it and probably can not fix it because some of the data you need was probably on the space that you took away.&lt;BR /&gt;</description>
    <pubDate>Wed, 21 Jan 2009 00:15:19 GMT</pubDate>
    <dc:creator>Heironimus</dc:creator>
    <dc:date>2009-01-21T00:15:19Z</dc:date>
    <item>
      <title>XEN disk file corrupt</title>
      <link>https://community.hpe.com/t5/operating-system-linux/xen-disk-file-corrupt/m-p/4341122#M34915</link>
      <description>XEN disk file corrupt&lt;BR /&gt;&lt;BR /&gt;dom0 OS: SLES 10 SP2&lt;BR /&gt;domU OS(paravirtual guest): SLES 10 SP2&lt;BR /&gt;SAN: HP HSV 200, FC connected&lt;BR /&gt;&lt;BR /&gt;Problem&lt;BR /&gt;domU(SLES10 SP2) doesn't boots/start, after reducing the size of FC connected SAN disk, /dev/mapper/3600508b40006e2cc0000c000005d0000 (before it was 350 GB, then after reduction it is 250 GB)&lt;BR /&gt;&lt;BR /&gt;in dom0,&lt;BR /&gt;/dev/mapper/3600508b40006e2cc0000c000005d0000 mounted on /var/lib/xen/images&lt;BR /&gt;&lt;BR /&gt;# cd /var/lib/xen/images/sles10-1so&lt;BR /&gt;# fdisk -l disk0&lt;BR /&gt;&lt;NO output=""&gt;&lt;BR /&gt;# du -h fdisk&lt;BR /&gt;6.5G disk0&lt;BR /&gt;&lt;BR /&gt;then I ran fsck in dom0&lt;BR /&gt;# reiserfsck --rebuild-tree dev/mapper/3600508b40006e2cc0000c000005d0000&lt;BR /&gt;&lt;BR /&gt;Pass 0:&lt;BR /&gt;####### Pass 0 #######&lt;BR /&gt;Loading on-disk bitmap .. ok, 34700582 blocks marked used&lt;BR /&gt;Skipping 10450 blocks (super block, journal, bitmaps) 34690132 blocks will be read&lt;BR /&gt;0%block 203170: The number of items (15) is incorrect, should be (1) - corrected&lt;BR /&gt;block 203170: The free space (0) is incorrect, should be (3792) - corrected&lt;BR /&gt;pass0: vpf-10200: block 203170, item 0: The item [4096 16778752 0x100010003070000 IND (1)] with wrong offset is deleted&lt;BR /&gt;....20%....block 25657137: The number of items (59392) is incorrect, should be (1) - corrected&lt;BR /&gt;block 25657137: The free space (45944) is incorrect, should be (3792) - corrected&lt;BR /&gt;pass0: vpf-10110: block 25657137, item (0): Unknown item type found [4294858473 3733539071 0xe8e7894c ??? (15)] - deleted&lt;BR /&gt;&lt;BR /&gt;40%....60%....80%....100% left 0, 24326 /sec&lt;BR /&gt;12651 directory entries were hashed with "r5" hash.&lt;BR /&gt;"r5" hash is selected&lt;BR /&gt;Flushing..finished&lt;BR /&gt;Read blocks (but not data blocks) 34690132&lt;BR /&gt;Leaves among those 36693&lt;BR /&gt;- corrected leaves 1537&lt;BR /&gt;- leaves all contents of which could not be saved and del&lt;BR /&gt;pointers in indirect items to wrong area 1554648 (zeroed)&lt;BR /&gt;Objectids found 12654&lt;BR /&gt;&lt;BR /&gt;Pass 1 (will try to insert 36687 leaves):&lt;BR /&gt;####### Pass 1 #######&lt;BR /&gt;Looking for allocable blocks .. finished&lt;BR /&gt;0%....20%....40%....60%....80%....100% left 0, 203 /sec&lt;BR /&gt;Flushing..finished&lt;BR /&gt;36687 leaves read&lt;BR /&gt;36677 inserted&lt;BR /&gt;10 not inserted&lt;BR /&gt;####### Pass 2 #######&lt;BR /&gt;&lt;BR /&gt;Pass 2:&lt;BR /&gt;0%....20%....40%....60%....80%....100% left 0, 20 /sec&lt;BR /&gt;Flushing..finished&lt;BR /&gt;Leaves inserted item by item 10&lt;BR /&gt;Pass 3 (semantic):&lt;BR /&gt;####### Pass 3 #########&lt;BR /&gt;/sles10-1so/res/disk0vpf-10680: The file [29 34] has the wrong block count in the StatData (12582912) - corrected to (0)&lt;BR /&gt;Flushing..finished&lt;BR /&gt;Files found: 12193&lt;BR /&gt;Directories found: 460&lt;BR /&gt;Broken (of files/symlinks/others): 1&lt;BR /&gt;Pass 3a (looking for lost dir/files):&lt;BR /&gt;####### Pass 3a (lost+found pass) #########&lt;BR /&gt;Looking for lost directories:&lt;BR /&gt;Flushing..finishede 1, 0 /sec&lt;BR /&gt;Pass 4 - finished done 0, 0 /sec&lt;BR /&gt;Deleted unreachable items 1536&lt;BR /&gt;Flushing..finished&lt;BR /&gt;Syncing..finished&lt;BR /&gt;###########&lt;BR /&gt;reiserfsck finished at Thu Jan 15 12:53:58 2009&lt;BR /&gt;&lt;BR /&gt;but still domU doesnt start&lt;BR /&gt;# xm start -c sles10-1so&lt;BR /&gt;Using config file "./sles10-1so".&lt;BR /&gt;Error: Boot loader didn't return any data!&lt;BR /&gt;&lt;BR /&gt;# cd /var/lib/xen/images&lt;BR /&gt;# reiserfsck --check disk0&lt;BR /&gt;bread: End of file, cannot read the block (1572863).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;QUESTIONS:&lt;BR /&gt;--------&lt;BR /&gt;is there any possibility to recover/mend the disk file (disk0) ?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;when I ran fsck in dom0&lt;BR /&gt;# reiserfsck --rebuild-tree dev/mapper/3600508b40006e2cc0000c000005d0000&lt;BR /&gt;&lt;BR /&gt;fsck reports that it has recovered the filesystem then why xen disk is still not recovered ?&lt;BR /&gt;&lt;BR /&gt;and please confirm, If i reduce the disk size of a san disk ? file system will become corrupt ?&lt;BR /&gt;&lt;BR /&gt;Thanks and Regards&lt;/NO&gt;</description>
      <pubDate>Tue, 20 Jan 2009 12:26:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/xen-disk-file-corrupt/m-p/4341122#M34915</guid>
      <dc:creator>Maaz</dc:creator>
      <dc:date>2009-01-20T12:26:17Z</dc:date>
    </item>
    <item>
      <title>Re: XEN disk file corrupt</title>
      <link>https://community.hpe.com/t5/operating-system-linux/xen-disk-file-corrupt/m-p/4341123#M34916</link>
      <description>Did you reduce the filesystem before you reduced the SAN volume? If you made the SAN volume smaller than the filesystem then you did corrupt it and probably can not fix it because some of the data you need was probably on the space that you took away.&lt;BR /&gt;</description>
      <pubDate>Wed, 21 Jan 2009 00:15:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/xen-disk-file-corrupt/m-p/4341123#M34916</guid>
      <dc:creator>Heironimus</dc:creator>
      <dc:date>2009-01-21T00:15:19Z</dc:date>
    </item>
  </channel>
</rss>

