On Sat, 2009-12-05 at 16:18 -0800, Linda Walsh wrote:

Frans de Boer wrote:

...

Dear All,

I have tried to use 11.2 installed on a ext4 partition.

---

Might try 'xfs'. ??

Works pretty reliably. Don't know if ext4 has 15+ years of maturity and development behind it, but is still used for real-time performance and that supported access control lists and extended attributes over 10 years ago.

-l Thanks Linda,

I think I stick with ext3. And no, ext4 is only recently introduced in the kernel. By the way, reiserfs was also given unreliable results. Only ext3 has proven itself on my system for the last 8(?) years or so. But I'll wait because someone might have a solution of some other kind. Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-12-05 at 16:18 -0800, Linda Walsh wrote:

...

I have tried to use 11.2 installed on a ext4 partition.

---

Might try 'xfs'. ??

Xfs on / requires a separate /boot partition formatted as ext2. You might get it working without this, but it is not guaranteed. I use ext3 for / and xfs for /home. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAksa/8YACgkQtTMYHG2NR9WKBgCdFsW+g902EHEkSpFig5yEG5N/ OEkAnjuvKYYwvOekpIwyBGCz2dzEZuMj =wBHB -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 2009/12/06 03:24 (GMT+0100) Frans de Boer composed:

On Sun, 2009-12-06 at 01:50 +0100, Carlos E. R. wrote:

...

Xfs on / requires a separate /boot partition formatted as ext2. You might get it working without this, but it is not guaranteed.

...

I use ext3 for / and xfs for /home.

Still, nobody has experienced the same?

Also, my /boot partition is ext3. I just wonder, what is the benefiet of using xfs above ext3?

What's the benefit of a journal on a /boot partition? All my /boots are ext2. All my others are ext3, except for those on which I store iso files, which are also ext2. -- " We have no government armed with power capable of contending with human passions unbridled by morality and religion." John Adams, 2nd US President Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Saturday 05 December 2009 21:24:01 Frans de Boer wrote:

On Sun, 2009-12-06 at 01:50 +0100, Carlos E. R. wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Saturday, 2009-12-05 at 16:18 -0800, Linda Walsh wrote:

...

...

I have tried to use 11.2 installed on a ext4 partition.

--- Might try 'xfs'. ??

Xfs on / requires a separate /boot partition formatted as ext2. You might get it working without this, but it is not guaranteed.

I use ext3 for / and xfs for /home.

Still, nobody has experienced the same?

Also, my /boot partition is ext3. I just wonder, what is the benefiet of using xfs above ext3?

Frans.

Hi Frans, I have experienced such 'ghost' files in the past. The entire '/' filesystem would eventually become corrupted and I'd have to 'wipe the slate clean' and reinstall. This turned out to be a **hardware specific** problem (chipset / host controller module + hard drive firmware) that could be triggered in one of two ways: a) combining disparate filesystem types on the same drive. As I recall, double-buffering was default enabled with some filesystem types and not others. The symptoms went away when I selected a single filesystem type for use in all partitions on that drive, i.e. all reiserfs or all ext3 or all ext2, and so on, b) installing into an existing '/' partition without first mounting it and deleting all the contents. To reiterate, this experience was **hardware specific** so YMMV. hth & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sunday 06 December 2009 06:13:06 Carlos E. R. wrote:

...

 a) combining disparate filesystem types on the same drive. As I recall, double-buffering was default enabled with some filesystem types and not others.

I think double-buffering canbe disabled :-?

That's the way it's supposed to work, but I enabled and disabled double- buffering with no joy. The only way I could get that drive to cooperate was by using the same filesystem type in each partition. The OP may have better luck, though. In my case I've already upgraded the hardware. ;-) Thx! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sat, Dec 5, 2009 at 21:24, Frans de Boer wrote:

Still, nobody has experienced the same?

Installing openSUSE 11.2 I see EXT4 is now the default and think to myself "Hmmm, there is no way this is as reliable and bug-free as the old tried-and-tested EXT3." So I installed with EXT3 and have no problems whatsoever -- even KDE4 seems to behave fine. Med Vennlig Hilsen, A. Helge Joakimsen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sunday 06 Dec 2009 00:50:12 Carlos E. R. wrote:

On Saturday, 2009-12-05 at 16:18 -0800, Linda Walsh wrote:

...

...

I have tried to use 11.2 installed on a ext4 partition.

--- Might try 'xfs'. ??

Xfs on / requires a separate /boot partition formatted as ext2. You might get it working without this, but it is not guaranteed.

I use ext3 for / and xfs for /home.

XFS on / and /home here and NO ext* anywhere to be found at all could not move from it fast enough i use Reiserfs on the boot partition with no problems at all have done for some time now Pete . -- Powered by openSUSE 11.2 Milestone 2 (x86_64) Kernel: 2.6.30-rc6-git3-4- default KDE: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 1" 09:20 up 14 days 23:09, 3 users, load average: 0.78, 0.62, 0.48

On Sunday 06 Dec 2009 11:17:21 Carlos E. R. wrote:

On Sunday, 2009-12-06 at 09:22 -0000, Peter Nikolic wrote:

...

On Sunday 06 Dec 2009 00:50:12 Carlos E. R. wrote:

...

I use ext3 for / and xfs for /home.

XFS on / and /home here and NO ext* anywhere to be found at all could not move from it fast enough i use Reiserfs on the boot partition with no problems at all have done for some time now

That's because you don't hibernate your machine. Hibernation where the boot device is reiserfs does no longer work, since at least 11.1 (grub can't cope). There is a bugzilla for that one, with a quite small chance of being solved.

Humm well i aint likley to either AFAIAK the machine is either on and running or off i dont and never will use hibernate dont see the point of it Pete . -- Powered by openSUSE 11.2 Milestone 2 (x86_64) Kernel: 2.6.30-rc6-git3-4- default KDE: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 1" 14:55 up 15 days 4:45, 3 users, load average: 0.06, 0.06, 0.09

On Sunday 06 Dec 2009 16:13:02 Carlos E. R. wrote:

On Sunday, 2009-12-06 at 14:57 -0000, Peter Nikolic wrote:

...

Humm well i aint likley to either AFAIAK the machine is either on and running or off i dont and never will use hibernate dont see the point of it

Botting: 2 or 3 minutes. Login and session setup: 1 minute Starting all applications and loading files: several minutes.

vs:

Thawing with everything opened in the same place: 30 seconds.

Is that enough of a point? :-)

Nope cus on my Compaq Presario V5030 i get nothing like that lenght of time from cold 1.2 mins tops and now that the graphical boot is behaving quicker than that cus i dont have the init3 login init5 bit but i suggest you look at hardware if it's that slow even my old 32bit Athlon box is quicker than that . Pete . -- Powered by openSUSE 11.2 Milestone 2 (x86_64) Kernel: 2.6.30-rc6-git3-4- default KDE: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 1" 16:36 up 15 days 6:26, 3 users, load average: 1.02, 0.86, 0.74

On Sunday 06 Dec 2009 16:57:11 Carlos E. R. wrote:

On Sunday, 2009-12-06 at 16:39 -0000, Peter Nikolic wrote:

Hardware is fine. I use more apps than you do. One of them, the UPS daemon (upsmon) takes a full minute to start and verify things. Plus, opening the files I was working last time in, say, openoffice takes time. And I have to open a lot of apps, manually.

Also, my ups monitor hibernates the machine in case of power failure.

How com upsmon now takes a full minute to come up it never used to when i ran a UPS back in the TCP/IP Packet days when i ran GB7NJR , I run the Openoffice quickstarter all the time as well i have Kmail , Korganizer , Kaddressbook , Kpgp all loading this is on KDE4.3.1 with 8 activities setup and running each with it's own wallpaper so something sounds a little off there . Pete -- Powered by openSUSE 11.2 Milestone 2 (x86_64) Kernel: 2.6.30-rc6-git3-4- default KDE: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 1" 18:51 up 15 days 8:41, 3 users, load average: 0.96, 0.64, 0.57

On Sunday 06 December 2009 05:17:21 Carlos E. R. wrote:

On Sunday, 2009-12-06 at 09:22 -0000, Peter Nikolic wrote:

...

On Sunday 06 Dec 2009 00:50:12 Carlos E. R. wrote:

...

I use ext3 for / and xfs for /home.

XFS on / and /home here and NO ext* anywhere to be found at all could not move from it fast enough i use Reiserfs on the boot partition with no problems at all have done for some time now

That's because you don't hibernate your machine. Hibernation where the boot device is reiserfs does no longer work, since at least 11.1 (grub can't cope). There is a bugzilla for that one, with a quite small chance of being solved.

That's odd. I've hibernated and resumed this system 3-4 times since I did a "hard reboot". bss@dellbuntu:~% uname -a Linux dellbuntu 2.6.31.5-0.1-default #1 SMP 2009-10-26 15:49:03 +0100 x86_64 x86_64 x86_64 GNU/Linux bss@dellbuntu:~% df -PTh Filesystem Type Size Used Avail Use% Mounted on /dev/dm-3 reiserfs 12G 8.0G 4.1G 67% / udev tmpfs 1000M 2.1M 998M 1% /dev /dev/sda1 reiserfs 2.1G 62M 2.1G 3% /boot /dev/dm-2 reiserfs 60G 38G 23G 63% /home /dev/dm-0 reiserfs 1.0G 66M 959M 7% /usr/local /tmp tmpfs 1000M 64K 1000M 1% /tmp bss@dellbuntu:~% rpm -qa | grep -i grub grub-0.97-162.2.x86_64 bss@dellbuntu:~% uptime 16:41pm up 26 days 5:59, 5 users, load average: 0.30, 0.59, 1.08 bss@dellbuntu:~% It's a laptop; I suspend to RAM multiple times a day, and suspend to Disk at least once a week. [307260.889174] Suspending console(s) (use no_console_suspend to debug) [307262.044283] ricoh-mmc: Suspending. [308166.750541] Suspending console(s) (use no_console_suspend to debug) [308167.896194] ricoh-mmc: Suspending. [332009.116566] Suspending console(s) (use no_console_suspend to debug) [332010.256179] ricoh-mmc: Suspending. [356200.832386] Suspending console(s) (use no_console_suspend to debug) [356200.932200] ricoh-mmc: Suspending. [373228.746944] Suspending console(s) (use no_console_suspend to debug) [373229.900184] ricoh-mmc: Suspending. [377700.398636] Suspending console(s) (use no_console_suspend to debug) [377701.564391] ricoh-mmc: Suspending. [378651.661153] Suspending console(s) (use no_console_suspend to debug) [378652.812197] ricoh-mmc: Suspending. [403252.456896] Suspending console(s) (use no_console_suspend to debug) [403253.616402] ricoh-mmc: Suspending. [406099.329769] Suspending console(s) (use no_console_suspend to debug) [406099.636193] ricoh-mmc: Suspending. [409300.842429] Suspending console(s) (use no_console_suspend to debug) [409301.988196] ricoh-mmc: Suspending. [410588.178278] Suspending console(s) (use no_console_suspend to debug) [410588.484195] ricoh-mmc: Suspending. [411819.716298] Suspending console(s) (use no_console_suspend to debug) [411820.864181] ricoh-mmc: Suspending. [414938.795932] Suspending console(s) (use no_console_suspend to debug) [414939.208182] ricoh-mmc: Suspending. [445741.057240] Suspending console(s) (use no_console_suspend to debug) [445741.264182] ricoh-mmc: Suspending. bss@dellbuntu:~% -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/

On Monday 07 December 2009 18:35:51 Carlos E. R. wrote:

On Monday, 2009-12-07 at 16:43 -0600, Boyd Stephen Smith Jr. wrote:

...

...

That's because you don't hibernate your machine. Hibernation where the boot device is reiserfs does no longer work, since at least 11.1 (grub can't cope). There is a bugzilla for that one, with a quite small chance of being solved.

That's odd. I've hibernated and resumed this system 3-4 times since I did a "hard reboot".

/dev/dm-3 reiserfs 12G 8.0G 4.1G 67% / /dev/sda1 reiserfs 2.1G 62M 2.1G 3% /boot

Which suse version?

IIRC, installed from the oS 11.1 CD. I've since upgraded to 11.2 via manual massaging of my repositories followed by a zypper dup, an unbootable system, and later recovery.

That is indeed very surprising. Is /boot mounted "ro" perhaps? Something different?

(Forgive the long lines.) bss@dellbuntu:~% cat /etc/fstab UUID=5fac269a-4f32-453e-b62f-75585ac4b11a /boot reiserfs acl,user_xattr 1 2 UUID=dc09155b-b57a-4242-9985-ed7cdbc833c5 / reiserfs acl,user_xattr 1 1 UUID=eb76202f-3520-4162-bc88-5f9e9ee4f02b /home reiserfs acl,user_xattr 1 2 UUID=1c0018de-e186-4f73-bc1c-c8ee1f966212 /usr/local reiserfs acl,user_xattr 1 2 /dev/dellbuntu/swap swap swap defaults 0 0 tmp /tmp tmpfs defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 bss@dellbuntu:~% sudo cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Tue Nov 10 23:36:59 CST 2009 # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader # Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader default 0 timeout 8 ##YaST - generic_mbr gfxmenu (hd0,0)/message ##YaST - activate ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 11.2 root (hd0,0) kernel /vmlinuz-2.6.31.5-0.1-default root=/dev/disk/by-uuid/dc09155b-b57a-4242-9985- ed7cdbc833c5 resume=/dev/dellbuntu/swap splash=silent quiet showopts vga=0x31b initrd /initrd-2.6.31.5-0.1-default ###Don't change this comment - YaST2 identifier: Original name: Debian GNU/Linux, kernel 2.6.24-etchnhalf.1-amd64 (/dev/sda3)### title Debian GNU/Linux, kernel 2.6.24-etchnhalf.1-amd64 (/dev/sda3) rootnoverify (hd0,2) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (fd0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 11.2 root (hd0,0) kernel /vmlinuz-2.6.31.5-0.1-default root=/dev/disk/by-uuid/dc09155b-b57a-4242-9985- ed7cdbc833c5 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe I don't think the Debian installation actually works anymore. I had Debian installed prior to the oS 11.1 installation.

Please have a look at Bugzilla 538795.

It's possible that my GRUB stage 1 is still lingering from a Debian installation. I don't think that would be the case, since grub has been installed / reinstalled multiple times since then. I don't have a long delay during boot-up or thaw, but my /boot is rather small so the journal replay may be quick. When thawing, the longest period of time is taken reading (and decompressing?) the system image. It is unfortunate that reiserfs is dying/dead. It has served me well on multiple pieces of hardware, and ext4 is not a solution for me (although ext2 /boot is acceptable). I will eventually move to XFS if I have problems with reiserfs while BTrFS is still unstable. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/

Hi friend, I saw your ticket about the Ghost, so I have a question about this. If we can use the Symantec Ghost 11 to make a image of the whole disk of the OS ,then recover it onto a new disk? Would you pls give me any idea of it ? thanks Regards Kalvin Weng AT&S (China) Co.,Ltd Tel.: +86 21 24080509 Email: k.weng@cn.ats.net "Boyd Stephen Smith Jr." opensuse@opensuse.org cc 2009-12-08 09:30 "Carlos E. R." Subject Re: [opensuse] Re: 11.2 has buildtin Ghost? On Monday 07 December 2009 18:35:51 Carlos E. R. wrote:

On Monday, 2009-12-07 at 16:43 -0600, Boyd Stephen Smith Jr. wrote:

...

...

That's because you don't hibernate your machine. Hibernation where the boot device is reiserfs does no longer work, since at least 11.1 (grub can't cope). There is a bugzilla for that one, with a quite small chance of being solved.

That's odd. I've hibernated and resumed this system 3-4 times since I did a "hard reboot".

/dev/dm-3 reiserfs 12G 8.0G 4.1G 67% / /dev/sda1 reiserfs 2.1G 62M 2.1G 3% /boot

Which suse version?

IIRC, installed from the oS 11.1 CD. I've since upgraded to 11.2 via manual massaging of my repositories followed by a zypper dup, an unbootable system, and later recovery.

That is indeed very surprising. Is /boot mounted "ro" perhaps? Something different?

(Forgive the long lines.) bss@dellbuntu:~% cat /etc/fstab UUID=5fac269a-4f32-453e-b62f-75585ac4b11a /boot reiserfs acl,user_xattr 1 2 UUID=dc09155b-b57a-4242-9985-ed7cdbc833c5 / reiserfs acl,user_xattr 1 1 UUID=eb76202f-3520-4162-bc88-5f9e9ee4f02b /home reiserfs acl,user_xattr 1 2 UUID=1c0018de-e186-4f73-bc1c-c8ee1f966212 /usr/local reiserfs acl,user_xattr 1 2 /dev/dellbuntu/swap swap swap defaults 0 0 tmp /tmp tmpfs defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 bss@dellbuntu:~% sudo cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Tue Nov 10 23:36:59 CST 2009 # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader # Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader default 0 timeout 8 ##YaST - generic_mbr gfxmenu (hd0,0)/message ##YaST - activate ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 11.2 root (hd0,0) kernel /vmlinuz-2.6.31.5-0.1-default root=/dev/disk/by-uuid/dc09155b-b57a-4242-9985- ed7cdbc833c5 resume=/dev/dellbuntu/swap splash=silent quiet showopts vga=0x31b initrd /initrd-2.6.31.5-0.1-default ###Don't change this comment - YaST2 identifier: Original name: Debian GNU/Linux, kernel 2.6.24-etchnhalf.1-amd64 (/dev/sda3)### title Debian GNU/Linux, kernel 2.6.24-etchnhalf.1-amd64 (/dev/sda3) rootnoverify (hd0,2) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (fd0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 11.2 root (hd0,0) kernel /vmlinuz-2.6.31.5-0.1-default root=/dev/disk/by-uuid/dc09155b-b57a-4242-9985- ed7cdbc833c5 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe I don't think the Debian installation actually works anymore. I had Debian installed prior to the oS 11.1 installation.

Please have a look at Bugzilla 538795.

It's possible that my GRUB stage 1 is still lingering from a Debian installation. I don't think that would be the case, since grub has been installed / reinstalled multiple times since then. I don't have a long delay during boot-up or thaw, but my /boot is rather small so the journal replay may be quick. When thawing, the longest period of time is taken reading (and decompressing?) the system image. It is unfortunate that reiserfs is dying/dead. It has served me well on multiple pieces of hardware, and ext4 is not a solution for me (although ext2 /boot is acceptable). I will eventually move to XFS if I have problems with reiserfs while BTrFS is still unstable. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/ (See attached file: signature.asc) This e-mail and any attachment may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.