Mailinglist Archive: opensuse-factory (626 mails)
| < Previous | Next > |
Re: [opensuse-factory] 11.0 default filesystems again
- From: Sid Boyce <sboyce@xxxxxxxxxxxxxxxx>
- Date: Mon, 03 Mar 2008 03:59:53 +0000
- Message-id: <47CB77B9.8080306@xxxxxxxxxxxxxxxx>
Eberhard Moenkeberg wrote:
Soooooo.... what you are saying here is that ext3 is broke and I should open bugs for 10.3 and 11.0 Alpha2. The 2 instances I related do not indicate solidity. Accidental power loss should only result in replaying the journal.
May be in the PC world such things are acceptible, but I could see mayhem if I were depending on a laptop that had to do fsck.ext3 while carrying out maintenance on a mainframe or large SPARC server. I think, really I know for sure that Mr. Customer would seriously become bent out of shape. Luckily using SuSE/reiserfs I have had no such worry or problem over many years, bleeding edge everything and still rock solid.
Reminds me of a laugh British Airways shared with me about Sun's pitch on Concurrent Maintenance which they were touting as a big plus. Scenario put to Sun, box has a hardware hit. Sun says, blacklist the failing hardware, reboot Solaris and they would change the failing bit without powering the system down, so the customer would suffer no downtime. BA says, "but I would suffer a loss of service whether or not you have to power the system down, my mainframes keep on running when they take hardware hits" -- Sun was stuck for an answer.
The answer I suppose is down to the amount of grief you can tolerate.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
Hi,Only 30-40 minutes? Depends of course on the CPU speed and amount of memory. So typically terrabytes is a question of how long is a piece of string.
On Sun, 2 Mar 2008, Juan Erbes wrote:
2008/2/22, Andreas Jaeger <aj@xxxxxxx>:
Sid Boyce <sboyce@xxxxxxxxxxxxxxxx> writes:
> Not wishing to reopen old flames and wounds, but in the last 2 days IThe new kernel for Opensuse 11 has support for ReiserFS4?
> have had problems with ext3. On this 11.0 Alpha2 box I have
> /dev/sdb1 as / (JFS) 500G SATA
> /dev/sdb2 /boot (reiserfs)
> /dev/sda1 /ftp (ext3) 320G SATA
> Suddenly there was a system freeze that needed a hard reset and when
> booting, after the grub selection, a black screen appeared. I had to
> boot from 11.0 Alpha2 CD and run fsck. The ext3 partition was the one
> with the problem and it took ages to get through. The fsck for the
> reiserfs and JFS were all clean.
>
> Last night on a box belonging to a relative on which I did a fresh
> 10.3 install to a new HD /dev/sda1 (160G PATA ext3), with the old 10.0
> HD as /dev/sdb2 (80G PATA reiserfs), I inadvertently pulled the wrong
> plug and powered the box off. The ext3 drive drive took over an hour
> to fix, the reiserfs drive took minutes, complaining of 3 errors,
> quickly fixed with --fix-fixable.
>
> Is there any chance we could have JFS as an install choice for 11.0?
Isn't JFS available in 10.3 - just with a big warning that it's
untested?
What is about the support of ReiserFS4 as default file system in Opensuse 11?
I have now in my system (workstation) ext3, and from time to time when
it executes the automatic fsck (60 days), it takes about 40 minutes
for a hard disk of 250 GB, and in many of this cases, I hate only 30
minutes to see the emails and go out.
With ReiserFS3, I not hate those problems to wait for use the
workstation 30 or 40 minutes, as with ext3 happens.
I love the solidity of ext3.
If it does check (wasting your time), you have a far better chance to
"survive" against the others.
Viele Grüße
Eberhard Mönkeberg (emoenke@xxxxxxx, em@xxxxxxx)
Soooooo.... what you are saying here is that ext3 is broke and I should open bugs for 10.3 and 11.0 Alpha2. The 2 instances I related do not indicate solidity. Accidental power loss should only result in replaying the journal.
May be in the PC world such things are acceptible, but I could see mayhem if I were depending on a laptop that had to do fsck.ext3 while carrying out maintenance on a mainframe or large SPARC server. I think, really I know for sure that Mr. Customer would seriously become bent out of shape. Luckily using SuSE/reiserfs I have had no such worry or problem over many years, bleeding edge everything and still rock solid.
Reminds me of a laugh British Airways shared with me about Sun's pitch on Concurrent Maintenance which they were touting as a big plus. Scenario put to Sun, box has a hardware hit. Sun says, blacklist the failing hardware, reboot Solaris and they would change the failing bit without powering the system down, so the customer would suffer no downtime. BA says, "but I would suffer a loss of service whether or not you have to power the system down, my mainframes keep on running when they take hardware hits" -- Sun was stuck for an answer.
The answer I suppose is down to the amount of grief you can tolerate.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |