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