Hello
I have noticed something "strange" happens when using the parameter
dom0_mem
.
I use a SLES11 SP2 with kernel 3.0.13-0.27-xen x86_64 where grub parameters
are ''kernel /xen.gz vga=mode-0x317 dom0_mem=1024M''
The computer has 4GB RAM, which runs one DomU 2GB RAM (backuppc)
When I run the command ''du'' or ''fsck'' in the
dom0, these commands behave
erroneous.
the command ''du'' run on a usb external hard disk error tells
me:
du: cannot access `/mnt/copia/.....'': Input/output error
This is done randomly, 1st see indicates an error and does not indicate the
2nd mistake. This makes it usb disk or a SATA drive connected to the
motherboard.
After fsck indicates that the filesystem is inconsistent, indicating errors
Inode 2154525 has illegal block(s). Clear<y>?
Inode 1393089 has EXTENTS_FL flag set on filesystem without extents
support.
Inode 8460056 has a extra size (14394) which is invalid
Fix<y>? ye
Inode 8460057 has imagic flag set. Clear<y>? yes
Inode 8460059 has a extra size (14394) which is invalid
Fix<y>? yes
Inode 8460049 has compression flag set on filesystem without
compression support. Clear<y>? yes
Inode 8460049 has INDEX_FL flag set but is not a directory.
Clear HTree index<y>? yes
Inode 8460049, i_size is 10405922140023030687, should be 0.
Fix<y>? yes
(errors are several different times)
Reaching the dom0_mem conclucion that produces much change took me hard,
reinstallation of OS and many twists and turns.
Any suggestions you can produce?
There is a hardware error, because by using the same hardware and run the
fsck produces no errors
As always thanks for reading this far down .. and excuse the English,
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
Alexandre Kouznetsov
2013-Jul-22 22:46 UTC
Re: dom0_mem parameter produces errors fsck and du command
Hello. El 22/07/13 15:56, Flako escribió:> Hello > I have noticed something "strange" happens when using the parameter > dom0_mem. > > I use a SLES11 SP2 with kernel 3.0.13-0.27-xen x86_64 where grub > parameters are ''kernel /xen.gz vga=mode-0x317 dom0_mem=1024M'' > The computer has 4GB RAM, which runs one DomU 2GB RAM (backuppc) > > When I run the command ''du'' or ''fsck'' in the dom0, these commands behave > erroneous.What makes you to relate those errors with dom0_mem parameter? (in any case, bad memory CAN manifest itself as corrupt data on the disk)> Any suggestions you can produce? > There is a hardware error, because by using the same hardware and run > the fsck produces no errorsFind it out. Make sure your RAM is ok running a memtest86 on it. Check your disk with badblocks. -- Alexandre Kouznetsov
2013/7/22 Alexandre Kouznetsov <alk@ondore.com>> Hello. > > El 22/07/13 15:56, Flako escribió: > > Hello >> I have noticed something "strange" happens when using the parameter >> dom0_mem. >> >> I use a SLES11 SP2 with kernel 3.0.13-0.27-xen x86_64 where grub >> parameters are ''kernel /xen.gz vga=mode-0x317 dom0_mem=1024M'' >> The computer has 4GB RAM, which runs one DomU 2GB RAM (backuppc) >> >> When I run the command ''du'' or ''fsck'' in the dom0, these commands behave >> erroneous. >> > What makes you to relate those errors with dom0_mem parameter? > (in any case, bad memory CAN manifest itself as corrupt data on the disk) > > > Any suggestions you can produce? >> There is a hardware error, because by using the same hardware and run >> the fsck produces no errors >> > Find it out. > > Make sure your RAM is ok running a memtest86 on it. > Check your disk with badblocks. > > -- > Alexandre Kouznetsov > >Hi Alexandre, I''m sure it produces dom0_mem because: -Change all full hard (motherboard, hard disk, RAM, power supply) and reinstall the OS from scratch but still fails fsck - The disks before using the check with badblocks and smartctl. - If I start a livecd on it hard, there is no fsck error - If you start a non-xen kernel (same kernel without xen enabled) is not fsck error occurs - If you reboot with xen kernel without dom0_mem parameter error occurs not fsck - Memtest shows no errors (but I could not let it go more than one pass) Apparently there is a hardware problem (although it could be incompatibility), It happens when using dom0_mem, but I can not understand why. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Alexandre Kouznetsov
2013-Jul-23 16:49 UTC
Re: dom0_mem parameter produces errors fsck and du command
El 23/07/13 06:43, Flako escribió:> Hi Alexandre, > I''m sure it produces dom0_mem because: > > -Change all full hard (motherboard, hard disk, RAM, power supply) and > reinstall the OS from scratch but still fails fsck > - The disks before using the check with badblocks and smartctl. > - If I start a livecd on it hard, there is no fsck error > - If you start a non-xen kernel (same kernel without xen enabled) is not > fsck error occurs > - If you reboot with xen kernel without dom0_mem parameter error occurs > not fsck > - Memtest shows no errors (but I could not let it go more than one pass)The component you have not switched yet, as I understand it, is CPU. Let''s suppose that "du" works fine as is, and give the error because of filesystem inconsistency. I understand you have tested this issue with a external USB disk and with your local SATA disk. Maybe they are not unmounted cleanly on reboot? Weired enough, though. -- Alexandre Kouznetsov
2013/7/23 Alexandre Kouznetsov <alk@ondore.com>> El 23/07/13 06:43, Flako escribió: > > Hi Alexandre, >> I''m sure it produces dom0_mem because: >> >> -Change all full hard (motherboard, hard disk, RAM, power supply) and >> reinstall the OS from scratch but still fails fsck >> - The disks before using the check with badblocks and smartctl. >> - If I start a livecd on it hard, there is no fsck error >> - If you start a non-xen kernel (same kernel without xen enabled) is not >> fsck error occurs >> - If you reboot with xen kernel without dom0_mem parameter error occurs >> not fsck >> - Memtest shows no errors (but I could not let it go more than one pass) >> > The component you have not switched yet, as I understand it, is CPU. > > Let''s suppose that "du" works fine as is, and give the error because of > filesystem inconsistency. I understand you have tested this issue with a > external USB disk and with your local SATA disk. Maybe they are not > unmounted cleanly on reboot? > > Weired enough, though. > > > -- > Alexandre Kouznetsov > > >Hi Alexandre: The cpu also change it (I lack specify). I do not think the problem is the result of a bad unmount because a manually performed. I mention the test case that focuses on dom0_mem: 1. Check the usb disk in another pc and it shows no errors 2. Check the usb disk with kernel-xen with dom0_mem and it shows errors (do not select repair, because the inconsistent process leaves the filesystem) 3. Check the usb disk with kernel-xen without dom0_mem and this does not show errors April. Check the usb disk in another PC with or without kernel-xen and this shows no errors. Something that comment is that the usb disk is encrypted with cryptsetup (1.0.6-pre1), but fsck failures the note from the hard SATTA (to indicate in the other mail) that I tried it with and without cryptsetup cryptsetup. Perform many other tests, but as previously thought was hardware issue or OS''s is like the case of tests that indicated it seems more complete. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Alexandre Kouznetsov
2013-Jul-23 21:08 UTC
Re: dom0_mem parameter produces errors fsck and du command
Hello. El 23/07/13 15:57, Flako escribió:> Perform many other tests, but as previously thought was hardware issue > or OS''s is like the case of tests that indicated it seems more complete.I give up, no clue. Fill a bug report http://en.opensuse.org/openSUSE:Submitting_bug_reports -- Alexandre Kouznetsov
2013/7/23 Alexandre Kouznetsov <alk@ondore.com>> Hello. > > El 23/07/13 15:57, Flako escribió: > > Perform many other tests, but as previously thought was hardware issue >> or OS''s is like the case of tests that indicated it seems more complete. >> > > I give up, no clue. > > Fill a bug report http://en.opensuse.org/**openSUSE:Submitting_bug_** > reports <http://en.opensuse.org/openSUSE:Submitting_bug_reports> > > >Alexandre Kouznetsov Alexandre: If I make a bug report, because it''s weird .. and I have a good test case :) Thanks for responding. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users