Re: [Bug 391975] Re: XFS incompatible with RAID0: Information get corrupted when Reading and Writting on Raid0 XFS partition over (N-1)*StripeSize [Only writes to N-1 stripes ovelaping info when writt
Sorry i can not because i use no more XFS, now i use EXT4 over Linux Software Raid0 over three HDDs... no more XFS, also i have updated to last Ubuntu 2010/8/13 Fabio Marconi marconifa...@hotmail.it Hello Luis Lumbreras Picazo Can you please attach here these files: /var/log/syslog /var/log/dmesg /var/log/kern.log /var/log/boot.log Thanks :)Fabio ** Package changed: ubuntu = linux (Ubuntu) -- XFS incompatible with RAID0: Information get corrupted when Reading and Writting on Raid0 XFS partition over (N-1)*StripeSize [Only writes to N-1 stripes ovelaping info when writting to block over (N-1)*Size/N, also one stripe is not used at read time] https://bugs.launchpad.net/bugs/391975 You received this bug notification because you are a direct subscriber of the bug. Status in “linux” package in Ubuntu: Incomplete Bug description: UPDATED: Fail localized more specifically - when writing / reading from Raid0 when XFS partition format. At read time one stripe is not used (maybe last?), so when you write to a block over (N-1)*Size/N the information on partition get corrupted, what i have not checked is where the info writted really goes, i think it also does not write on last stripe and info is overlaped, because with some little writes a los of directories, structure is corrupted. Since what i could see when only write to a block number lower than (N-1)*Size/N the information on partition do not get corrupted and can be read after correctly, but when write to a block number higher than (N-1)*Size/N the information on partition get corrupted, directory structure also get corrupted. Also reads seems to read only from N-1 stripes, because speed is always (N-1)/N when XFS over Raid0, but with EXT2/3/4 over same exact Raid0 the speed is very near to N/N. I mean if used N stripes, speed is N*SpeedOfStripe when EXT2/3/4, but with XFS it is (N-1)*SpeedOfStripe and since zcav reads at block level the partition format must not affect read speed because read is not at partition format level, it is at block level. Hope now is all clear. Have in mind whart i have done to ensure this: Install one and another ... times Ubuntu ... One per each test*configuration, too many hours, this night i have not dream just to make this checks... But if there is needed anything else... just ask me for them, ok? Now i also have been able to reproduce such on VirtualBox it would take less time to make more tests, since i can install Ubuntu, while checking on another Virtual... I have checked this with the next configurations (first three on real hardware, next on VirtualBOX): Two stripes: /dev/sda1 - For Raid0 /dev/sdb1 - For Raid0 /dev/md0 - Composed of /dev/sda1 and /dev/sdb1, formatted as XFS RESULT of zcav - Read speed is 1/2 of what must be, and 1/2 of what is if formatted as EXT4 Three stripes: /dev/sda1 - For Raid0 /dev/sdb1 - For Raid0 /dev/sdc1 - For Raid0 /dev/md0 - Composed of /dev/sda1, /dev/sdb1 and /dev/sdc1, formatted as XFS RESULT of zcav - Read speed is 2/3 of what must be, and 2/3 of what is if formatted as EXT4 Four stripes: /dev/sda1 - For Raid0 /dev/sdb1 - For Raid0 /dev/sdc1 - For Raid0 /dev/sdd1 - For Raid0 /dev/md0 - Composed of /dev/sda1, /dev/sdb1, /dev/sdc1 and /dev/sdd1, formatted as XFS RESULT of zcav - Read speed is 3/4 of what must be, and 3/4 of what is if formatted as EXT4 This next ones only checked on VirtulBox: Five Stripes: Same idea, add /dev/sde1 to /dev/md0 with RESULT of zcav - Read speed is 4/5 ... Six Stripes: Same idea, add /dev/sdf1 to /dev/md0 with RESULT of zcav - Read speed is 5/6 ... Seven Stripes: Same idea, add /dev/sdg1 to /dev/md0 with RESULT of zcav - Read speed is 6/7 ... Eight Stripes: Same idea, add /dev/sdh1 to /dev/md0 with RESULT of zcav - Read speed is 7/8 ... Nine Stripes: Same idea, add /dev/sdi1 to /dev/md0 with RESULT of zcav - Read speed is 8/9 ... Ten Stripes: Same idea, add /dev/sdj1 to /dev/md0 with RESULT of zcav - Read speed is 9/10 ... ..etc.. Up to 33 stripes (maximun i can with VirtualBox). In all cases it worked perfectly until a write on blocks with number higher to (N-1)*StripesSize, all writes to blocks with number higher to (N-1)*StripesSize makes the partition get corrupted. -- - I let below, the old text (with some little corrections just to correct missmatchs), so can be seen a little history how i got to this problem and so what have i check. --- -- I will try to explain as much detail as i can the BUG, because it is very critical, makes you to loose all data while working and do not let to recover anything, neither to reinstall without deleting all partitions on all HDDs. So, sorry me if this is a long text and if i repeat somethings, my intention is let as most clear as possible why it is Very Critical and how easy and severe
Re: [Bug 366397] Re: swapon hangs when using file on kernels 2.6.28-13 and 2.6.28-11 but works perfect on kernel 2.6.27.11
Sorry me, since a lot of time i do not use anymore SWAP on files,... since i detected the error. Now i do not have such FAT32 partition with pagefile.sys, now i use a dedicated SWAP partition, so i am afraid i can not check it on new kernels, sorry. If i have time i will try to see if i can re-check it on my old PC... with last kernel from Ubuntu... but i can not know when i will have time to do it, since i must re-format... and reinstall all from scratch. Now i have all my Linux using full HDDs in Linux Raid 0 configurations... so it will be very diffucult to me to make a hole for a FAT32 parttiion... one PC with Two HDDs, the other with Three HDDs, all in Raid 0... as follows: -Each start part of each HDD for / (Raid0) -Little part of each HDD for SWAP (No Raid0, instead same priority) -Rest of each HDD for /media/MyDATA (Raid0) Speed is much greater,... too much better speed... So i am afraid if i want to use a full 4GB FAT32 partition with a pagefile.sys file been used as SWAP i must destroy Raid 0 configuration... and i do not want to need to reinstall my whole Linux and applications... so i am afraid i can not re-check it anymore, sorry. But anyone can do such re-check... anyone who has a non Raid0 system... The steps: -Create a 4GB primary parttition -Format it as FAT32 -Boot Windows and let it create a pagefile.sys as greater as it lets, nar 4GB but not 4GB - if i do not remember bad between 4050MiB and 4090MiB, of course size is not a power of 2 -Restart -Run Linux and configure it to use such file as the only SWAP to be used -At next boot it hangs... or better said swapon is what hangs I could see such error on some kernels 2.6.28-11 and up till i decided to use dedicated partitions, and Raid0 fo / and /media/MyDATA... Sorry, now i can not check it again if i do not re-format my HDDs loosing all Linux configuration and applications installed... but if i have time i will try to see if i can try with old external USB HDD i have... it has one FAT32 partition with more than 4GB free space on it, so maybe... but will not be the exact same test... so not sure if can be considered a valid test. Now i am trying to solve other problems, like poweroff on Ubuntu Karmic 64bits on a HP Pavilion tx2620es (32bit version power off correctly, while 64bit version does all except final power cut, so still remain on and must be pressed near 4sec the power button to power off it completly) and some other problems... so i do not have much time left to test something i will not use anymore: SWAP on a file. Sorry for any inconvenience... but why not someone else do such tests? For me now it will imply to throught out all my Linux installation system, configuration and applications... since now i use Linux Raid0 by software for / ... etc. -- swapon hangs when using file on kernels 2.6.28-13 and 2.6.28-11 but works perfect on kernel 2.6.27.11 https://bugs.launchpad.net/bugs/366397 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234954] Re: No powerdown upon shutdown on Lenovo 6469-22R (3000 Y200)
I have the same problem, but it seems to be a gdm problem, not related with acpi nor with apm... le te mexplain why: If i tell it to hybernate it power off at end of it and when powered on again it resumes well. If i tell it to shutdown it does not power off at end, but hey only if gdm was running when asked. More detailed: If gdm is running and i open a terminal window: no way to power off after shutdown, none commands: shutdown, halt --poweroff,... none works If gdm is running and i press Ctrl+Alt+F2 to go to a console at full screen (text mode), but i let gdm running: no way to power off after shutdown, none commands: shutdown, halt --poweroff,... none works But, if i press Ctrl+Alt+F2 to go to a console at full screen (text mode), and do: #sudo /etc/init.d/gdm stop So gdm is stopped then after few secconds i can confirm it is stopped with [ps -A | grep gdm], so i ask to shutdown with: #sudo halt --poweroff Or with shutdown,... all of them at end turns off the power and power off the notebook correctly. I have seen on Internet a lot of forums on where they tell something about acpi=force, apm=power-off,... on /boot/grub/menu.lst also about adding apm to modules,... etc. none of that works for me. And i found that if gdm is not running when calling shutdown it power off correctly. When i was using Ubuntu Intrepid Ibex and Ubuntu Jaunty Jackalope it allways power off correctly, but when i updated to Ubuntu Karmic Koala it starts to not do the final power off when shutdown... now i know the cause is gdm running when calling shutdown. Maybe it is related in some way with Kernel or with propietary ATI graphics driver... Also i can see some near identical lines (more than ten) on /var/messages at the end of it with this error: Kernel: Assertion fail in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_rs780.0 at line: 53 I do not know if such error is related with the shutdown problem, but is the last error logged and it is at end ot /var/messages no more lines after it... but i can only see it when not powered off correctly, if i do the trick of stoping gdm it does not appear. Hope this can help someone to fix-it. Till them i will do the trick of Ctrl+Alt+F2 - login - password - sudo /etc/init.d/gdm stop - sudo halt --poweroff Note: After doing such, i powered on again and then after some hours of work i press shutdown by mistake (did not remember ro do the trick stop gdm then halt --poweroff) but what surprise! it turns off the notebook correctly... so when i have time i will re-check if it was only once or can be reproduced. I mean: -Power On, then tell destop menu to shutdown normally and check if it turns off. -If not force turn off, then turn on again, do the trick of stopping gdm and halt --poweroff, then power on again then tell destop menu to shutdown normally and check if it turns off. But i will not have time till weekend, so if any one can also check that, it would be great. SOLUTION THAT WORKS FOR ME: Ctrl+Alt+F2 - Login - Password - sudo /etc/init.d/gdm stop - sudo halt --poweroff -- No powerdown upon shutdown on Lenovo 6469-22R (3000 Y200) https://bugs.launchpad.net/bugs/234954 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227844] Re: shutdown hangs (sometimes) - Hardy 64 - ASUS P5LD2 SE
I have the same problem, but it seems to be a gdm problem, not related with acpi nor with apm... le te mexplain why: If i tell it to hybernate it power off at end of it and when powered on again it resumes well. If i tell it to shutdown it does not power off at end, but hey only if gdm was running when asked. More detailed: If gdm is running and i open a terminal window: no way to power off after shutdown, none commands: shutdown, halt --poweroff,... none works If gdm is running and i press Ctrl+Alt+F2 to go to a console at full screen (text mode), but i let gdm running: no way to power off after shutdown, none commands: shutdown, halt --poweroff,... none works But, if i press Ctrl+Alt+F2 to go to a console at full screen (text mode), and do: #sudo /etc/init.d/gdm stop So gdm is stopped then after few secconds i can confirm it is stopped with [ps -A | grep gdm], so i ask to shutdown with: #sudo halt --poweroff Or with shutdown,... all of them at end turns off the power and power off the notebook correctly. I have seen on Internet a lot of forums on where they tell something about acpi=force, apm=power-off,... on /boot/grub/menu.lst also about adding apm to modules,... etc. none of that works for me. And i found that if gdm is not running when calling shutdown it power off correctly. When i was using Ubuntu Intrepid Ibex and Ubuntu Jaunty Jackalope it allways power off correctly, but when i updated to Ubuntu Karmic Koala it starts to not do the final power off when shutdown... now i know the cause is gdm running when calling shutdown. Maybe it is related in some way with Kernel or with propietary ATI graphics driver... Also i can see some near identical lines (more than ten) on /var/messages at the end of it with this error: Kernel: Assertion fail in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_rs780.0 at line: 53 I do not know if such error is related with the shutdown problem, but is the last error logged and it is at end ot /var/messages no more lines after it... but i can only see it when not powered off correctly, if i do the trick of stoping gdm it does not appear. Hope this can help someone to fix-it. Till them i will do the trick of Ctrl+Alt+F2 - login - password - sudo /etc/init.d/gdm stop - sudo halt --poweroff Note: After doing such, i powered on again and then after some hours of work i press shutdown by mistake (did not remember ro do the trick stop gdm then halt --poweroff) but what surprise! it turns off the notebook correctly... so when i have time i will re-check if it was only once or can be reproduced. I mean: -Power On, then tell destop menu to shutdown normally and check if it turns off. -If not force turn off, then turn on again, do the trick of stopping gdm and halt --poweroff, then power on again then tell destop menu to shutdown normally and check if it turns off. But i will not have time till weekend, so if any one can also check that, it would be great. SOLUTION THAT WORKS FOR ME: Ctrl+Alt+F2 - Login - Password - sudo /etc/init.d/gdm stop - sudo halt --poweroff -- shutdown hangs (sometimes) - Hardy 64 - ASUS P5LD2 SE https://bugs.launchpad.net/bugs/227844 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98790] Re: shutdown can't auto poweroff PC
I have the same problem, but it seems to be a gdm problem, not related with acpi nor with apm... le te mexplain why: If i tell it to hybernate it power off at end of it and when powered on again it resumes well. If i tell it to shutdown it does not power off at end, but hey only if gdm was running when asked. More detailed: If gdm is running and i open a terminal window: no way to power off after shutdown, none commands: shutdown, halt --poweroff,... none works If gdm is running and i press Ctrl+Alt+F2 to go to a console at full screen (text mode), but i let gdm running: no way to power off after shutdown, none commands: shutdown, halt --poweroff,... none works But, if i press Ctrl+Alt+F2 to go to a console at full screen (text mode), and do: #sudo /etc/init.d/gdm stop So gdm is stopped then after few secconds i can confirm it is stopped with [ps -A | grep gdm], so i ask to shutdown with: #sudo halt --poweroff Or with shutdown,... all of them at end turns off the power and power off the notebook correctly. I have seen on Internet a lot of forums on where they tell something about acpi=force, apm=power-off,... on /boot/grub/menu.lst also about adding apm to modules,... etc. none of that works for me. And i found that if gdm is not running when calling shutdown it power off correctly. When i was using Ubuntu Intrepid Ibex and Ubuntu Jaunty Jackalope it allways power off correctly, but when i updated to Ubuntu Karmic Koala it starts to not do the final power off when shutdown... now i know the cause is gdm running when calling shutdown. Maybe it is related in some way with Kernel or with propietary ATI graphics driver... Also i can see some near identical lines (more than ten) on /var/messages at the end of it with this error: Kernel: Assertion fail in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_rs780.0 at line: 53 I do not know if such error is related with the shutdown problem, but is the last error logged and it is at end ot /var/messages no more lines after it... but i can only see it when not powered off correctly, if i do the trick of stoping gdm it does not appear. Hope this can help someone to fix-it. Till them i will do the trick of Ctrl+Alt+F2 - login - password - sudo /etc/init.d/gdm stop - sudo halt --poweroff Note: After doing such, i powered on again and then after some hours of work i press shutdown by mistake (did not remember ro do the trick stop gdm then halt --poweroff) but what surprise! it turns off the notebook correctly... so when i have time i will re-check if it was only once or can be reproduced. I mean: -Power On, then tell destop menu to shutdown normally and check if it turns off. -If not force turn off, then turn on again, do the trick of stopping gdm and halt --poweroff, then power on again then tell destop menu to shutdown normally and check if it turns off. But i will not have time till weekend, so if any one can also check that, it would be great. SOLUTION THAT WORKS FOR ME: Ctrl+Alt+F2 - Login - Password - sudo /etc/init.d/gdm stop - sudo halt --poweroff -- shutdown can't auto poweroff PC https://bugs.launchpad.net/bugs/98790 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 44008] Re: Shutdown still doesn't turn off my computer
I have the same problem, but it seems to be a gdm problem, not related with acpi nor with apm... le te mexplain why: If i tell it to hybernate it power off at end of it and when powered on again it resumes well. If i tell it to shutdown it does not power off at end, but hey only if gdm was running when asked. More detailed: If gdm is running and i open a terminal window: no way to power off after shutdown, none commands: shutdown, halt --poweroff,... none works If gdm is running and i press Ctrl+Alt+F2 to go to a console at full screen (text mode), but i let gdm running: no way to power off after shutdown, none commands: shutdown, halt --poweroff,... none works But, if i press Ctrl+Alt+F2 to go to a console at full screen (text mode), and do: #sudo /etc/init.d/gdm stop So gdm is stopped then after few secconds i can confirm it is stopped with [ps -A | grep gdm], so i ask to shutdown with: #sudo halt --poweroff Or with shutdown,... all of them at end turns off the power and power off the notebook correctly. I have seen on Internet a lot of forums on where they tell something about acpi=force, apm=power-off,... on /boot/grub/menu.lst also about adding apm to modules,... etc. none of that works for me. And i found that if gdm is not running when calling shutdown it power off correctly. When i was using Ubuntu Intrepid Ibex and Ubuntu Jaunty Jackalope it allways power off correctly, but when i updated to Ubuntu Karmic Koala it starts to not do the final power off when shutdown... now i know the cause is gdm running when calling shutdown. Maybe it is related in some way with Kernel or with propietary ATI graphics driver... Also i can see some near identical lines (more than ten) on /var/messages at the end of it with this error: Kernel: Assertion fail in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_rs780.0 at line: 53 I do not know if such error is related with the shutdown problem, but is the last error logged and it is at end ot /var/messages no more lines after it... but i can only see it when not powered off correctly, if i do the trick of stoping gdm it does not appear. Hope this can help someone to fix-it. Till them i will do the trick of Ctrl+Alt+F2 - login - password - sudo /etc/init.d/gdm stop - sudo halt --poweroff Note: After doing such, i powered on again and then after some hours of work i press shutdown by mistake (did not remember ro do the trick stop gdm then halt --poweroff) but what surprise! it turns off the notebook correctly... so when i have time i will re-check if it was only once or can be reproduced. I mean: -Power On, then tell destop menu to shutdown normally and check if it turns off. -If not force turn off, then turn on again, do the trick of stopping gdm and halt --poweroff, then power on again then tell destop menu to shutdown normally and check if it turns off. But i will not have time till weekend, so if any one can also check that, it would be great. SOLUTION THAT WORKS FOR ME: Ctrl+Alt+F2 - Login - Password - sudo /etc/init.d/gdm stop - sudo halt --poweroff -- Shutdown still doesn't turn off my computer https://bugs.launchpad.net/bugs/44008 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 439282] Re: does not power down the system properly
I have the same problem, but it seems to be a gdm problem, not related with acpi nor with apm... le te mexplain why: If i tell it to hybernate it power off at end of it and when powered on again it resumes well. If i tell it to shutdown it does not power off at end, but hey only if gdm was running when asked. More detailed: If gdm is running and i open a terminal window: no way to power off after shutdown, none commands: shutdown, halt --poweroff,... none works If gdm is running and i press Ctrl+Alt+F2 to go to a console at full screen (text mode), but i let gdm running: no way to power off after shutdown, none commands: shutdown, halt --poweroff,... none works But, if i press Ctrl+Alt+F2 to go to a console at full screen (text mode), and do: #sudo /etc/init.d/gdm stop So gdm is stopped then after few secconds i can confirm it is stopped with [ps -A | grep gdm], so i ask to shutdown with: #sudo halt --poweroff Or with shutdown,... all of them at end turns off the power and power off the notebook correctly. I have seen on Internet a lot of forums on where they tell something about acpi=force, apm=power-off,... on /boot/grub/menu.lst also about adding apm to modules,... etc. none of that works for me. And i found that if gdm is not running when calling shutdown it power off correctly. When i was using Ubuntu Intrepid Ibex and Ubuntu Jaunty Jackalope it allways power off correctly, but when i updated to Ubuntu Karmic Koala it starts to not do the final power off when shutdown... now i know the cause is gdm running when calling shutdown. Maybe it is related in some way with Kernel or with propietary ATI graphics driver... Also i can see some near identical lines (more than ten) on /var/messages at the end of it with this error: Kernel: Assertion fail in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_rs780.0 at line: 53 I do not know if such error is related with the shutdown problem, but is the last error logged and it is at end ot /var/messages no more lines after it... but i can only see it when not powered off correctly, if i do the trick of stoping gdm it does not appear. Hope this can help someone to fix-it. Till them i will do the trick of Ctrl+Alt+F2 - login - password - sudo /etc/init.d/gdm stop - sudo halt --poweroff Note: After doing such, i powered on again and then after some hours of work i press shutdown by mistake (did not remember ro do the trick stop gdm then halt --poweroff) but what surprise! it turns off the notebook correctly... so when i have time i will re-check if it was only once or can be reproduced. I mean: -Power On, then tell destop menu to shutdown normally and check if it turns off. -If not force turn off, then turn on again, do the trick of stopping gdm and halt --poweroff, then power on again then tell destop menu to shutdown normally and check if it turns off. But i will not have time till weekend, so if any one can also check that, it would be great. SOLUTION THAT WORKS FOR ME: Ctrl+Alt+F2 - Login - Password - sudo /etc/init.d/gdm stop - sudo halt --poweroff -- does not power down the system properly https://bugs.launchpad.net/bugs/439282 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 391975] [NEW] System get corrupted when Updating Pakages on Raid0 XFS system partition
Public bug reported: I will try to explain as much detail as i can the BUG, because it is very critical, makes you to loose all data while working and do not let to recover anything, neither to reinstall without deleting all partitions on all HDDs. So, sorry me if this is a long text and if i repeat somethings, my intention is let as most clear as possible why it is Very Critical and how easy and severe is and how to be able to reproduce it All times i tried with XFS i got a non working OS when updating pakages. I mean: When updating packeges an error occurs and icons on desktop disappear, also bars icons changes, wallpaper disapear ... not able to open a new console, ... data on hdd and memory get corrupted and after reboot, obviously the system can not boot, system partition get totaly corrupted and unrecoverable. This error only happens (only tested with XFS and EXT4 by now) if the system partition is XFS over Three HDDs on Raid0, not if it is EXT4; rest types (EXT3, EXT2, ReiserFX, JFS, ... not tested, since with EXT4 worked fine and i did not havd time to test). Let me try to explain how i have partitioned the three HDDs (do not ask me why, i have my reasons and security for data is nor importat, i make external BackUPs of what i consider important, internal HDDs are only for OS and temporal data, so speed is top most important, more because i use huge file proccesing, fils bigger than 25GB each, and a lot of them): So this is how i partition my HDDs just to get the top most speed on boot and work: /dev/sda: /dev/sda1 - Radi0 stripe 0 for / /dev/sda2 - Raid0 stripe 0 for /media/PersonalDATA /dev/sdb: /dev/sdb1 - SWAP for SWAP /dev/sdb2 - Raid0 stripe 1 for / /dev/sdb3 - Raid0 stripe 1 for /media/PersonalDATA /dev/sdc: /dev/sdc1 - ext3 for /boot /dev/sdc2 - SWAP for SWAP /dev/sdc3 - Raid0 stripe 2 for / /dev/sdc4 - Raid0 stripe 2 for /media/PersonalDATA /dev/md0: Composed of /dev/sda1, /dev/sdb2 and /dev/sdc3 and formated as XFS, mount point / /dev/md1: Composed of /dev/sda2, /dev/sdb3 and /dev/sdc4 and formated as EXT3, mount point /media/PersonalDATA Sizes of partitions are as follows: /boot of 512MB, / of 24GB and SWAPs as big as needed just to equal size for /media/PersonalDATA on all three HDDs, the rest. Let me put an example how i calculate sizes on for example PATA HDD near 80GB, SATA HDDs 81GB so: /boot - 512MB on SATA / - 24GB striped along all three HDDs (Raid0) two SWAP partitions, one on each SATA PATA one 80GB - 24/3 - 72GB, so size for /media/PersonalDATA is 72GB * 3 = 216GB One SATA 81GB - 512MB - 80.5GB; 80.5GB - 24/3 - 72.5GB; 72.5GB - 72GB - 0.5 for SWAP Other SATA 81GB - 0MB - 81GB; 81GB - 24/3 - 73GB; 73GB - 72GB - 1GB for SWAP Result: /boot - 512MB SWAP1 - 512MB SWAP2 - 1024MB / - 8GB*3 Raid0 - 24GB /media/PersonalDATA - 72GB*3 Raid0 - 216GB Each HDDs reports on zcav quite similar speeds, about 57MB/s on fast part and 30MB/s on slower part Note: zcav report near 57MB/s*3-171MB/s (Really about 155MB/S) when not XFS is selected for partition Note: zcav report much less than 57MB/s*3-171MB/s (Really about 102MB/S) when XFS is selected for partition I think this indicates a big an serious problem. With this configuration system install from CD ends correctly, reboot and system works perfect except for: Since the error makes system unuseable any more and needed to reinstall from scracth i think it is a serious problem with XFS. Extra: On another machine with only two HDDs it works perfect Raid0 with XFS for system gives no problem (till now, hopes it will not give problems on future, but who knows?). But if i use Three HDDs it is unuseable, all times error occur when updating packages, why? i don't know. It is reproductable 100% on all PCs i have tested. Let me explain how to reproduce this (allmost on three PCs i have tested it for four times on each with a result of 100% of times the error becomes and system stop working ata same point, installing packages updates): Steps fllowed to reproduce it: -Have a PC with on PATA HDD and three SATA HDDs of quite similar size -Delete all partitions on all (Three) HDDs [One PATA, Two SATA] -Create on PATA (/dev/sda) the next partitions: One for Raid0 for / (/dev/sda1) and another for Raid0 for /media/PersonalDATA (/dev/sda2) -Create on SATA (/dev/sdb) the next partitions: One for SWAP (/dev/sdb1), another for Raid0 for / (/dev/sdb2) and another for Raid0 for /media/PersonalDATA (/dev/sdb3) -Create on SATA (/dev/sdc) the next partitions: One for /boot (/dev/sdc1), another for SWAP (/dev/sdc2), another for Raid0 for / (/dev/sdc3) and another for Raid0 for /media/PersonalDATA (/dev/sdc4) -Create a Raid0 (/dev/md0) with /dev/sda1, /dev/sdb2 and /dev/sdc3 [for /] -Create a Raid0 (/dev/md1) with /dev/sda2, /dev/sdb3 and /dev/sdc4 [for /media/PersonalDATA] -Format /dev/md0 as XFS (that will cause problems after end installation, but if selected EXT4 no problem will be caused), mount point as / -Format /dev/md1 as
[Bug 366397] Re: swapon hangs when using file on kernels 2.6.28-13 and 2.6.28-11 but works perfect on kernel 2.6.27.11
** Summary changed: - swapon hangs when using file on kernel 2.6.28-11 but works perfect on kernel 2.6.27.11 + swapon hangs when using file on kernels 2.6.28-13 and 2.6.28-11 but works perfect on kernel 2.6.27.11 ** Description changed: I have tested a lot, changing VFAT (FAT32) umask, uid and gid on /etc/fstab, allways happens the same: - On kernel 2.6.28.11 swapon /media/SWAP/pagefile.sys hags, so at boot time it stops and Ctrl+Alt+Sup is only way to continue + On kernels 2.6.28.11 and 2.6.28.13 swapon /media/SWAP/pagefile.sys hags, so at boot time it stops and Ctrl+Alt+Sup is only way to continue On kernel 2.6.27-11 swapon /media/SWAP/pagefile.sys works perfectly. - Since i can select what kernel to load thanks to grub i cold do the next test: + Since i can select what kernel to load thanks to grub i can do the next + test with this results: + + -Boot selecting kernel 2.6.28-13 - swapon hangs the PC at boot time when activating swap area on file. + -Reboot with Ctrl+Alt+Sup + -Boot selecting kernel 2.6.28-13 - swapon hangs the PC at boot time when activating swap area on file. + -Reboot with Ctrl+Alt+Sup + ... so on as i select kernel 2.6.28-13 ... + -Boot selecting kernel 2.6.28-11 - swapon hangs the PC at boot time when activating swap area on file. -Reboot with Ctrl+Alt+Sup -Boot selecting kernel 2.6.28-11 - swapon hangs the PC at boot time when activating swap area on file. -Reboot with Ctrl+Alt+Sup ... so on as i select kernel 2.6.28-11 ... + -Boot selecting kernel 2.6.27-11 - swapon works perfect at boot time and activate swap area on file. -Shutdown Ubuntu 9.04 normaly + -Boot selecting kernel 2.6.28-11 - swapon hangs the PC at boot time when activating swap area on file. -Reboot with Ctrl+Alt+Sup -Boot selecting kernel 2.6.28-11 - swapon hangs the PC at boot time when activating swap area on file. -Reboot with Ctrl+Alt+Sup ... so on as i select kernel 2.6.28-11 ... + + -Boot selecting kernel 2.6.28-11 - swapon hangs the PC at boot time when activating swap area on file. + -Reboot with Ctrl+Alt+Sup + -Boot selecting kernel 2.6.28-11 - swapon hangs the PC at boot time when activating swap area on file. + -Reboot with Ctrl+Alt+Sup + ... so on as i select kernel 2.6.28-11 ... + -Boot selecting kernel 2.6.27-11 - swapon works perfect at boot time and activate swap area on file. -Shutdown Ubuntu 9.04 normaly - So i can see it only occurs when kernel 2.6.28-11 is selected. + So i can see it only occurs when kernel 2.6.28-11 is selected and also + when kernel 2.6.28-13 is selected. - Also i have commented swapon line, so i can boot with kernel 2.6.28-11, then i go to a prompt and type: + Also i have commented swapon line, so i can boot with kernels 2.6.28-11 + and 2.6.28-13, then i go to a prompt and type: + + + [Booting 2.6.28-13] + $uname -s -n -r -m + Linux ubuntu 2.6.28-13-generic i686 + $sudo swapon -s + [sudo] password for usuario: + Filename TypeSizeUsedPriority + $sudo mkswap /media/SWAP/pagefile.sys + $sudo swapon /media/SWAP/pagefile.sys + -- It hangs on swapon and console must be terminated, unable to kill swapon process, neither with kill -9 + + [Booting 2.6.28-11] + $uname -s -n -r -m + Linux ubuntu 2.6.28-11-generic i686 $sudo swapon -s [sudo] password for usuario: Filename TypeSizeUsedPriority $sudo mkswap /media/SWAP/pagefile.sys $sudo swapon /media/SWAP/pagefile.sys -- It hangs on swapon and console must be terminated, unable to kill swapon process, neither with kill -9 If i do the same but selecting kernel 2.6.27-11 at boot time i get: + $uname -s -n -r -m + Linux ubuntu 2.6.27-11-generic i686 $sudo swapon -s [sudo] password for usuario: Filename TypeSizeUsedPriority $sudo mkswap /media/SWAP/pagefile.sys $sudo swapon /media/SWAP/pagefile.sys $sudo swapon -s Filename TypeSizeUsedPriority /media/SWAP/pagefile.sysfile 4186104 0 -1 $ Obviously /media/SWAP is mounted as on both cases as: /dev/sda1 on /media/SWAP type vfat (rw,utf8,umask=007,uid=0,gid=0) Also the file pagefile.sys is defragmented. I have also done the next just to avoid any possible of being the content of the file: $sudo umount /media/SWAP $sudo mkfs.vfat -F 32 -n PAGEFILE -v /dev/sda1 $sudo mount /dev/sda1 /media/SWAP $sudo dd bs=1MB cont=4081 if=/dev/zero of=/media/SWAP/pagefile.sys $sudo mkswap /media/SWAP/pagefiles.sys $swapon /media/SWAP/pagefile.sys - If i do this on kernel 2.6.27-11 works perfect but if done in kernel 2.6.28-11 it hangs on swapon + If i do this on kernel 2.6.27-11 works perfect but if done in kernels 2.6.28-13 and 2.6.28-11 it hangs on swapon I think it is a kernel bug. Also i had tried to put sync command between commands, but
[Bug 366397] [NEW] swapon hangs when using file on kernel 2.6.28-11 but works perfect on kernel 2.6.27.11
Public bug reported: I have tested a lot, changing VFAT (FAT32) umask, uid and gid on /etc/fstab, allways happens the same: On kernel 2.6.28.11 swapon /media/SWAP/pagefile.sys hags, so at boot time it stops and Ctrl+Alt+Sup is only way to continue On kernel 2.6.27-11 swapon /media/SWAP/pagefile.sys works perfectly. Since i can select what kernel to load thanks to grub i cold do the next test: -Boot selecting kernel 2.6.28-11 - swapon hangs the PC at boot time when activating swap area on file. -Reboot with Ctrl+Alt+Sup -Boot selecting kernel 2.6.28-11 - swapon hangs the PC at boot time when activating swap area on file. -Reboot with Ctrl+Alt+Sup ... so on as i select kernel 2.6.28-11 ... -Boot selecting kernel 2.6.27-11 - swapon works perfect at boot time and activate swap area on file. -Shutdown Ubuntu 9.04 normaly -Boot selecting kernel 2.6.28-11 - swapon hangs the PC at boot time when activating swap area on file. -Reboot with Ctrl+Alt+Sup -Boot selecting kernel 2.6.28-11 - swapon hangs the PC at boot time when activating swap area on file. -Reboot with Ctrl+Alt+Sup ... so on as i select kernel 2.6.28-11 ... -Boot selecting kernel 2.6.27-11 - swapon works perfect at boot time and activate swap area on file. -Shutdown Ubuntu 9.04 normaly So i can see it only occurs when kernel 2.6.28-11 is selected. Also i have commented swapon line, so i can boot with kernel 2.6.28-11, then i go to a prompt and type: $sudo swapon -s [sudo] password for usuario: FilenameTypeSizeUsedPriority $sudo mkswap /media/SWAP/pagefile.sys $sudo swapon /media/SWAP/pagefile.sys -- It hangs on swapon and console must be terminated, unable to kill swapon process, neither with kill -9 If i do the same but selecting kernel 2.6.27-11 at boot time i get: $sudo swapon -s [sudo] password for usuario: FilenameTypeSizeUsedPriority $sudo mkswap /media/SWAP/pagefile.sys $sudo swapon /media/SWAP/pagefile.sys $sudo swapon -s FilenameTypeSizeUsedPriority /media/SWAP/pagefile.sysfile4186104 0 -1 $ Obviously /media/SWAP is mounted as on both cases as: /dev/sda1 on /media/SWAP type vfat (rw,utf8,umask=007,uid=0,gid=0) Also the file pagefile.sys is defragmented. I have also done the next just to avoid any possible of being the content of the file: $sudo umount /media/SWAP $sudo mkfs.vfat -F 32 -n PAGEFILE -v /dev/sda1 $sudo mount /dev/sda1 /media/SWAP $sudo dd bs=1MB cont=4081 if=/dev/zero of=/media/SWAP/pagefile.sys $sudo mkswap /media/SWAP/pagefiles.sys $swapon /media/SWAP/pagefile.sys If i do this on kernel 2.6.27-11 works perfect but if done in kernel 2.6.28-11 it hangs on swapon I think it is a kernel bug. Also i had tried to put sync command between commands, but same occurs swapon hangs on kernel 2.6.28-11 and on kernel 2.6.27-11 works fine. Hope this info could help to solve such bug. Thanks. ** Affects: ubuntu Importance: Undecided Status: New -- swapon hangs when using file on kernel 2.6.28-11 but works perfect on kernel 2.6.27.11 https://bugs.launchpad.net/bugs/366397 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
