On Sat, 2007-09-22 at 19:41 +0200, Stephan Kulow wrote:

Am Samstag 22 September 2007 schrieb Glenn Holmer:

...

On both a desktop (two tries) and a laptop machine, I was unable to complete the RC1 install. After the reboot, I get a brief flash of GUI, then he drops back to console. I see some "bus error" messages, and console won't accept "root" as login.

Anybody else seen something like this? I had no errors from Azureus when downloading the DVD, and used verify when burning with K3B.

You're using xfs as file system on all of these installations? Don't do that :)

Would all of you self righteous people stop telling others to _stop_ using the xfs file system? I've been using xfs successfully for many years _without one single_ problem. This even after numerous power outages because of a faulty UPS. If you are having problems take a good look at your hardware, especially your power supply, because that is where the problem is. If there were too many problems with xfs I am sure the powers that be would stop supplying it the distro. To the OP, it helps a great deal when you include the hardware involved. As has been stated many times on this list crystal balls are in short supply and seldom work when available. Also, have you tried the failsafe install/(upon first boot)? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Saturday 22 September 2007 15:12, Stephan Kulow wrote:

Am Samstag 22 September 2007 schrieb Kenneth Schneider:

...

Would all of you self righteous people stop telling others to _stop_ using the xfs file system? I've been using xfs successfully for many years _without one single_ problem. This even after numerous power outages because of a faulty UPS. If you are having problems take a good

Still this very problem _is_ caused by xfs. Everyone having had this problem so far could not reproduce a single problem when not using xfs. Even though the real problem is not the file system, but the fact that yast leaves it corrupted. ext3 and reiserfs seem to cope better with being corrupted though.

I'm confused by your response. Surely you're not saying that it's OK for YaST to corrupt the filesystem, and it's XFS' fault? I've also been using XFS for years, including previous betas of 10.3, without problems. Filed as 327521. -- "After the vintage season came the aftermath - and Cenbe." Glenn Holmer (Q-Link: ShadowM) http://www.lyonlabs.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Saturday 22 September 2007 16:15, Glenn Holmer wrote:

OK, I can see the details in 326942, which my issue was marked as a duplicate of within minutes.  Now I can breathe again... :)

The SUSE guys are everywhere ;-) -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Saturday 22 September 2007 14:57, Kenneth Schneider wrote:

On Sat, 2007-09-22 at 22:12 +0200, Stephan Kulow wrote:

...

...

Still this very problem _is_ caused by xfs. Everyone having had this problem so far could not reproduce a single problem when not using xfs. Even though the real problem is not the file system,

Here you contradict yourself. First you say the problem is "caused by xfs" then you say "the real problem is not the file system". So it would appear that the problem resides within YaST during the install process and not by the xfs filesystem. Report the problem properly and it will be solved properly.

Just a general note: File system corruption, like outright crashes, are never the fault of application- / user-level code, even if such code reliably triggers the untoward symptom. So if there's some kind of interaction between the pattern of use produced by this version of YaST and XFS, the culpability cannot be said to lie with YaST. For the record, I've been using XFS since whatever version of SuSE it was (9.something early, I think) that required you to provide the XFS driver via floppy 'cause it was accidentally left out of the kernel on the installer. It has given me no trouble whatsoever, and I live in an area that is prone to a few power failures each year. There were two just a couple of weeks ago on the same day, and my file systems survived just fine. (And yes, I'm shopping for a UPS...) By the way, Kenneth, you're putting a reply-to header in that directs replies back to opensuse@opensuse.org. Unless that was deliberate, it looks like some kind of copy-and-modify error that occurred when you set up you opensuse-factory mail folder. Randall Schulz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Saturday 22 September 2007 16:09, Kenneth Schneider wrote:

On Sat, 2007-09-22 at 15:16 -0700, Randall R Schulz wrote:

...

By the way, Kenneth, you're putting a reply-to header in that directs replies back to opensuse@opensuse.org. Unless that was deliberate, it looks like some kind of copy-and-modify error that occurred when you set up you opensuse-factory mail folder.

To reply-to was set by me because so many people don't know how to reply _just_ to the list. In this case I choose the wrong reply identity in Evolution.

It's a losing battle. People just cannot, will not, cannot be bothered to use email conscientiously. It's the same as driving and most other everyday activities. If you have to think about it, it's too much trouble. Life with your head up your ass is just _too_ comfortable!

Ken

Randall Schulz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Am Sonntag 23 September 2007 schrieb Carlos E. R.:

The Saturday 2007-09-22 at 22:12 +0200, Stephan Kulow wrote:

...

Still this very problem _is_ caused by xfs. Everyone having had this problem so far could not reproduce a single problem when not using xfs. Even though the real problem is not the file system, but the fact that yast leaves it corrupted. ext3 and reiserfs seem to cope better with being corrupted though.

Now that you mention it, I did get a corrupted reiserfs, after first boot during install. It appears the filesystem was not umounted properly before rebooting. Recovery was automatic, but it took enough time for me to notice. Several screens of it, actually.

Yes, reiserfs notices the corruption, corrects it and everything continues. Just as ext3 does. xfs lets yast crash - but I'm not allowed to claim xfs bugs on this list. Greetings, Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Am Sonntag 23 September 2007 schrieb Glenn Holmer:

On Sunday 23 September 2007 01:51, Stephan Kulow wrote:

...

Yes, reiserfs notices the corruption, corrects it and everything continues. Just as ext3 does. xfs lets yast crash - but I'm not allowed to claim xfs bugs on this list.

Earlier, you said

...

You're using xfs as file system on all of these installations? Don't do that :)

Is XFS a supported filesystem or not?

Supported filesystem as in yast lets you choose it? Yes, it is. If there are bugs in it, we'll remove the support from it in yast though (unless of course upstream kernel developers have a fix for it). Which is different to what we do when there is a bug in ext3 or reiserfs - then we're more likely to fix the problem ourselves. There is always a balance in features we can "support" - we can offer them if we believe they do not cause more problems than value. But that does not mean a fix for a problem ariving from it isn't removing the offering of the feature. But in this very case it is very pointless to discuss as the problem was mainly caused by xfs being different than being buggy. Fortunately we noticed the file corruptions in the other file systems, so the crash when using xfs was easily verified as fixed in not causing file system corruptions. Greetings, Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Sunday 23 September 2007 03:07, Carlos E. R. wrote:

The Saturday 2007-09-22 at 22:12 +0200, Stephan Kulow wrote:

...

Still this very problem _is_ caused by xfs. Everyone having had this problem so far could not reproduce a single problem when not using xfs. Even though the real problem is not the file system, but the fact that yast leaves it corrupted. ext3 and reiserfs seem to cope better with being corrupted though.

Now that you mention it, I did get a corrupted reiserfs, after first boot during install. It appears the filesystem was not umounted properly before rebooting. Recovery was automatic, but it took enough time for me to notice. Several screens of it, actually.

i can confirm this , clean install on a "old" aldi Medion portable , using reiserfs and KDE mini iso , i also noticed FS recovery after first reboot.

Seems to be bug 326478.

luc --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org