Hans de Bruin
2011-Jul-03 21:06 UTC
[Xen-users] Xen 4.1.1 DomU Partition table disappearing
I have just installed a new xen server: xen 4.1.1, 64bit xen/stable-2.6.32.x + USB pass throug patch, Atom D510. The first DomU I created is running fine, until I shut it down. At the moment the guest disappears from xentop, the partitiontable gets wiped out. I have checked this by running watch ''fdisk -l /dev/vg4/temp'' on Dom0 hex dump after shutdown: 0000000 3bc0 9839 0000 0200 0000 1b01 0000 0000 0000010 0000 0000 0000 0000 0000 0000 0000 0000 * 0000030 0000 0000 104e 52d4 5802 ca72 0000 0000 0000040 0000 0000 0000 0000 0000 0000 0000 0000 * 0100400 0001 0000 ffff 0003 0000 0000 1e76 a12d 0100410 b410 e54c cf9e 5c38 d250 37b0 0000 0000 0100420 0000 0000 0000 0000 0000 0000 0000 0000 * 0100ff0 0000 0000 0000 5753 5041 5053 4341 3245 0101000 0401 0000 0411 0000 0421 0000 547b 0000 0101010 01bf 0004 0000 0000 0000 0000 0000 74f4 0101020 0402 0000 0412 0000 0621 0000 0000 0000 0101030 024f 0004 0000 0000 0000 0000 0000 d53d 0101040 0403 0000 0413 0000 0821 0000 0000 0000 0101050 021f 0004 0000 0000 0000 0000 0000 737b 0101060 0404 0000 0414 0000 0a21 0000 0000 0d2c 0101070 00df 0004 0000 0000 0000 0000 0d2c ac78 0101080 0405 0000 0415 0000 0c21 0000 0000 2000 0101090 0000 0005 0000 0000 0000 0000 2000 a7e8 01010a0 0406 0000 0416 0000 0e21 0000 0000 2000 01010b0 0000 0005 0000 0000 0000 0000 2000 18c2 hexdump after repairing de partition table (1G swap, 15G ext4) 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 00001b0 0000 0000 0000 0000 81a1 ca45 0000 2000 00001c0 0021 aa82 8228 0800 0000 0000 0020 aa00 00001d0 8229 aa83 2802 0800 0020 f800 01df 0000 00001e0 0000 0000 0000 0000 0000 0000 0000 0000 00001f0 0000 0000 0000 0000 0000 0000 0000 aa55 0000200 0000 0000 0000 0000 0000 0000 0000 0000 * 0100400 0001 0000 ffff 0003 0000 0000 1e76 a12d 0100410 b410 e54c cf9e 5c38 d250 37b0 0000 0000 0100420 0000 0000 0000 0000 0000 0000 0000 0000 * 0100ff0 0000 0000 0000 5753 5041 5053 4341 3245 0101000 0401 0000 0411 0000 0421 0000 547b 0000 0101010 01bf 0004 0000 0000 0000 0000 0000 74f4 0101020 0402 0000 0412 0000 0621 0000 0000 0000 0101030 024f 0004 0000 0000 0000 0000 0000 d53d 0101040 0403 0000 0413 0000 0821 0000 0000 0000 0101050 021f 0004 0000 0000 0000 0000 0000 737b 0101060 0404 0000 0414 0000 0a21 0000 0000 0d2c 0101070 00df 0004 0000 0000 0000 0000 0d2c ac78 0101080 0405 0000 0415 0000 0c21 0000 0000 2000 -- Hans _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Message: 4 > Date: Sun, 03 Jul 2011 23:06:16 +0200 > From: Hans de Bruin <jmdebruin@xmsnet.nl> > Subject: [Xen-users] Xen 4.1.1 DomU Partition table disappearing > To: xen-users@lists.xensource.com > Message-ID: <4E10D9C8.3060204@xmsnet.nl> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I have just installed a new xen server: xen 4.1.1, 64bit > xen/stable-2.6.32.x + USB pass throug patch, Atom D510. > > The first DomU I created is running fine, until I shut it down. At the > moment the guest disappears from xentop, the partitiontable gets wiped > out. I have checked this by running watch ''fdisk -l /dev/vg4/temp'' on Dom0 >----snip---- Hello, Don''t have a solution here, but I have seen the same problem on one of my DomUs. Maybe if we compare our setups we''d find the cause. 1. Does your DomU run OpenSuSE (11.4)? 2. Is your DomU PV or HVM? 3. If HVM, are you running PV on HVM drivers? 4. Are you using LVM for your VM images? 5. Are you using LVM in your VM? 6. Have you tried using a separate distribution? 7. Have you tried creating another DomU to see if it exhibits the same problem? 8. Have you tried a different Dom0 kernel/xen? Basically I remember this problem came up with one of my xen/Dom0/DomU combinations, but didn''t have the chance to find out the root cause before moving on to another combination. Liwei _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hans de Bruin
2011-Jul-06 15:37 UTC
Re: [Xen-users] Xen 4.1.1 DomU Partition table disappearing
On 07/05/2011 04:32 AM, Liwei wrote:>> Message: 4 >> Date: Sun, 03 Jul 2011 23:06:16 +0200 >> From: Hans de Bruin<jmdebruin@xmsnet.nl> >> Subject: [Xen-users] Xen 4.1.1 DomU Partition table disappearing >> To: xen-users@lists.xensource.com >> Message-ID:<4E10D9C8.3060204@xmsnet.nl> >> Content-Type: text/plain; charset=ISO-8859-1; format=flowed >> >> I have just installed a new xen server: xen 4.1.1, 64bit >> xen/stable-2.6.32.x + USB pass throug patch, Atom D510. >> >> The first DomU I created is running fine, until I shut it down. At the >> moment the guest disappears from xentop, the partitiontable gets wiped >> out. I have checked this by running watch ''fdisk -l /dev/vg4/temp'' on Dom0 >> > ----snip---- > > Hello, > Don''t have a solution here, but I have seen the same problem on > one of my DomUs. Maybe if we compare our setups we''d find the cause. > 1. Does your DomU run OpenSuSE (11.4)?64 bit slackware 1337> 2. Is your DomU PV or HVM?My atom is not capable of hvm> 3. If HVM, are you running PV on HVM drivers? > 4. Are you using LVM for your VM images?yes, the volume group is on top of a linux software mirror> 5. Are you using LVM in your VM?no> 6. Have you tried using a separate distribution?not yet> 7. Have you tried creating another DomU to see if it exhibits the > same problem?not yet> 8. Have you tried a different Dom0 kernel/xen?not yet> Basically I remember this problem came up with one of my > xen/Dom0/DomU combinations, but didn''t have the chance to find out the > root cause before moving on to another combination. >I have done some tests using only the setup initrd from my slackware64 dvd. I filled another lvm block device with a lot of FF''s, and put it in front in the vm''s disk config. so the troubled partition table is on block device /dev/xvdb. After shutdown the FF''s on the first disk where all in tact, the partition table on de second disk was destroyed. So much for a workaround. So I went back to the normal configuration and tried to narrow down the exact time of destruction. To see the ammount of damage I filled the first 1000 512 byte blocks with FF''s and recreated the parition table. There are two primary partitions on the disk. 1G xvda1 for swap and xvda2 for the rest of the 16GB disk. What clears the partition table is: mount /dev/xvda2 /mnt some modification of /mnt like creating a directoy, or accessing a directory for the first time that day. And then the killer: sync So now there is a question number 9. have I tried differed file systems? not yet Some of the damage that is done: root@luna:/home/hans# hexdump -n 8000 /dev/vg4/temp 0000000 3bc0 9839 0000 0200 0000 2001 0000 0000 0000010 0000 0000 0000 0000 0000 0000 0000 0000 * 0000030 0000 0000 134e 9024 8336 8f46 0000 0000 0000040 0000 0000 0000 0000 0000 0000 0000 0000 * 0001000 ffff ffff ffff ffff ffff ffff ffff ffff * root@luna:/home/hans# hexdump -n 8000 /dev/vg4/temp 0000000 3bc0 9839 0000 0200 0000 2501 0000 0000 0000010 0000 0000 0000 0000 0000 0000 0000 0000 * 0000030 0000 0000 134e 6b28 2b2a f6fc 0000 0000 0000040 0000 0000 0000 0000 0000 0000 0000 0000 * 0001000 ffff ffff ffff ffff ffff ffff ffff ffff * 0001f40 So the first 0x01000 bytes get overwritten. That is the size of one memory page. It does not look like a ext4 supper block. -- Hans _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 6 July 2011 23:37, Hans de Bruin <jmdebruin@xmsnet.nl> wrote:>> Hello, >> Don''t have a solution here, but I have seen the same problem on >> one of my DomUs. Maybe if we compare our setups we''d find the cause. >> 1. Does your DomU run OpenSuSE (11.4)? > > 64 bit slackware 1337 > >> 2. Is your DomU PV or HVM? > > My atom is not capable of hvm > >> 3. If HVM, are you running PV on HVM drivers? >> 4. Are you using LVM for your VM images? > > yes, the volume group is on top of a linux software mirror > >> 5. Are you using LVM in your VM? > > no > >> 6. Have you tried using a separate distribution? > > not yet > >> 7. Have you tried creating another DomU to see if it exhibits the >> same problem? > > not yet > >> 8. Have you tried a different Dom0 kernel/xen? > > not yet > >> Basically I remember this problem came up with one of my >> xen/Dom0/DomU combinations, but didn''t have the chance to find out the >> root cause before moving on to another combination. >> > > I have done some tests using only the setup initrd from my slackware64 dvd. > I filled another lvm block device with a lot of FF''s, and put it in front in > the vm''s disk config. so the troubled partition table is on block device > /dev/xvdb. After shutdown the FF''s on the first disk where all in tact, the > partition table on de second disk was destroyed. So much for a workaround. > > So I went back to the normal configuration and tried to narrow down the > exact time of destruction. To see the ammount of damage I filled the first > 1000 512 byte blocks with FF''s and recreated the parition table. There are > two primary partitions on the disk. 1G xvda1 for swap and xvda2 for the rest > of the 16GB disk. What clears the partition table is: > > mount /dev/xvda2 /mnt > > some modification of /mnt like creating a directoy, or accessing a directory > for the first time that day. > > And then the killer: sync > > So now there is a question number 9. have I tried differed file systems? > > not yet > > Some of the damage that is done: > > root@luna:/home/hans# hexdump -n 8000 /dev/vg4/temp > 0000000 3bc0 9839 0000 0200 0000 2001 0000 0000 > 0000010 0000 0000 0000 0000 0000 0000 0000 0000 > * > 0000030 0000 0000 134e 9024 8336 8f46 0000 0000 > 0000040 0000 0000 0000 0000 0000 0000 0000 0000 > * > 0001000 ffff ffff ffff ffff ffff ffff ffff ffff > * > > root@luna:/home/hans# hexdump -n 8000 /dev/vg4/temp > 0000000 3bc0 9839 0000 0200 0000 2501 0000 0000 > 0000010 0000 0000 0000 0000 0000 0000 0000 0000 > * > 0000030 0000 0000 134e 6b28 2b2a f6fc 0000 0000 > 0000040 0000 0000 0000 0000 0000 0000 0000 0000 > * > 0001000 ffff ffff ffff ffff ffff ffff ffff ffff > * > 0001f40 > > So the first 0x01000 bytes get overwritten. That is the size of one memory > page. It does not look like a ext4 supper block. > > -- > Hans >I guess I won''t be of much help without digging too deeply (just achieved perfect setup on my machines, don''t want to mess it up). :-/ Though personally I''d recommend upgrading your distribution first, followed by xen and finally the Dom0 kernel, as I have the exact same problem as you, but one of the above solved it for me. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2011-Jul-07 02:34 UTC
Re: [Xen-users] Xen 4.1.1 DomU Partition table disappearing
On Wed, Jul 6, 2011 at 10:37 PM, Hans de Bruin <jmdebruin@xmsnet.nl> wrote:>>> The first DomU I created is running fine, until I shut it down. At the >>> moment the guest disappears from xentop, the partitiontable gets wiped >>> out. I have checked this by running watch ''fdisk -l /dev/vg4/temp'' on >>> Dom0 >>> >> ----snip---- >> >> Hello, >> Don''t have a solution here, but I have seen the same problem on >> one of my DomUs. Maybe if we compare our setups we''d find the cause. >> 1. Does your DomU run OpenSuSE (11.4)? > > 64 bit slackware 1337Check this thread on xen-devel: http://www.gossamer-threads.com/lists/xen/devel/212147 Looks similar, although the environment not identical. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hans de Bruin
2011-Jul-07 17:18 UTC
Re: [Xen-users] Xen 4.1.1 DomU Partition table disappearing
On 07/07/2011 04:34 AM, Fajar A. Nugraha wrote: > On Wed, Jul 6, 2011 at 10:37 PM, Hans de Bruin<jmdebruin@xmsnet.nl> wrote: >>>> The first DomU I created is running fine, until I shut it down. At the >>>> moment the guest disappears from xentop, the partitiontable gets wiped >>>> out. I have checked this by running watch ''fdisk -l /dev/vg4/temp'' on >>>> Dom0 ... >> >> 64 bit slackware 1337 > > Check this thread on xen-devel: > http://www.gossamer-threads.com/lists/xen/devel/212147 > > Looks similar, although the environment not identical. It is similar, thanks for pointing it out. -- Hans _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users