LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 10-25-2012, 12:08 AM   #16
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,413

Rep: Reputation: 857Reputation: 857Reputation: 857Reputation: 857Reputation: 857Reputation: 857Reputation: 857

he likes good muzak too http://bit.ly/RX8Sk8
 
Old 10-25-2012, 12:10 AM   #17
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 241

Rep: Reputation: 86
See https://lkml.org/lkml/2012/10/24/620
It's from the original reporter of the problem. He says for example: "It occurs to me that it is possible that this bug hits only those filesystems for which a umount has started but been unable to complete. If so, this is a relatively rare and unimportant bug which probably hits only me and users of slow removable filesystems in the whole world..." and "Verified! You do indeed need to do passing strange things to trigger this bug -- not surprising, really, or everyone and his dog would have reported it by now. As it is, I'm sorry this hit slashdot, because it reflects unnecessarily badly on a filesystem that is experiencing problems only when people do rather insane things to it."

So, it seems the bug bites if the system is rebooted or powered off while umount is running but has not yet finished.

I wouldn't change the filesystem quite yet...
 
1 members found this post helpful.
Old 10-25-2012, 12:19 AM   #18
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
I've always had especially bad luck with corrupting data and filesystem's with ext4. That's not to say it's necessarily the the file system's fault, just that it's happened numerous times to me. It's just never been very fault tolerant in my experience. I just now came back to ext4 because it seems like xfs will severely crunch my system for a moment during heavy read/write so it is disconcerting for bugs to be showing up. Anyway I'm not using supposedly affected kernels and I'm still not keeping data on ext4 so we shall see what happens.
 
Old 10-25-2012, 12:21 AM   #19
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
Quote:
Originally Posted by ponce View Post
he likes good muzak too http://bit.ly/RX8Sk8
HA! Ya gotta love a little Jello Lennon
 
1 members found this post helpful.
Old 10-25-2012, 02:27 AM   #20
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Another reason I don't use the popular ext* filesystems. They don't have a good history and it continues up to today.
 
Old 10-25-2012, 04:47 AM   #21
ppencho
LQ Newbie
 
Registered: Jan 2004
Location: Bulgaria
Distribution: Slackware64-current
Posts: 25

Rep: Reputation: 3
I don't know if this was related to the 'ext4' issue but I had a data loss (single file) 2-3 weeks ago. I was working on a project in Qt Creator when there was a power breakage. The UPS (APC but very old) saved me for few seconds but it switched off while PC was still powered. I don't remember the exact PC state at this moment: if I closed QT Creator or if I left KDE or if I started shutdown sequence, it happened so fast.
Next time I loaded the project one of the cpp files was empty (0 length).

I use Slackware64-current.
 
Old 10-25-2012, 05:18 AM   #22
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Gentoo
Posts: 15,438
Blog Entries: 2

Rep: Reputation: 4001Reputation: 4001Reputation: 4001Reputation: 4001Reputation: 4001Reputation: 4001Reputation: 4001Reputation: 4001Reputation: 4001Reputation: 4001Reputation: 4001
Quote:
Originally Posted by H_TeXMeX_H View Post
Another reason I don't use the popular ext* filesystems. They don't have a good history and it continues up to today.
I would maybe see it the other way around. Because they are popular more bugs are are reported, which gives them a "bad history", but makes them more stable in the end. Like this one occurs only under extreme conditions, but was found nonetheless.
 
3 members found this post helpful.
Old 10-25-2012, 06:07 AM   #23
Pixxt
Member
 
Registered: May 2008
Distribution: Slackware, Debian,
Posts: 102

Rep: Reputation: 17
Quote:
Originally Posted by jtsn View Post
Ext2 filesystem corruption was my main reason for switching mission-critical servers to BSD back in 2000 (and back to Slackware as ext3 settled in). So this is not the first time, but the continuation of a long sad story.
I quit using FreeBSD years ago around the 4.x-5.x series because it would not boot/ or boot and crash because i was using a usb keyboard and other oddities, besides that I never found FreeBSD to be more stable or faster than Linux. I do prefer some of its userland. FreeBSD and NetBSD newish init systems rock, it does not have the LP mess of Pulseaudio and SystemD but the kernels are are trash.

BSD users/devs are still the most elitist pricks this side of Apple. I would love to have a BSD like system with a Linux kernel, the closest I have come is Slackware.


Quote:
Originally Posted by H_TeXMeX_H View Post
Another reason I don't use the popular ext* filesystems. They don't have a good history and it continues up to today.
The EXT's are the least problematic general purpose filesystems in Linux, and better tested and a more bug free better track record than XFS, ReiserFS, JFS, BTRFS.
 
Old 10-25-2012, 06:58 AM   #24
gezley
Member
 
Registered: Sep 2009
Location: Ireland
Distribution: Slackware64, NetBSD
Posts: 490

Rep: Reputation: 207Reputation: 207Reputation: 207
Quote:
Originally Posted by Pixxt View Post
BSD users/devs are still the most elitist pricks this side of Apple.
Strong words. I don't consider myself elitist and I have found the NetBSD devs and users anything but elitist.
 
3 members found this post helpful.
Old 10-25-2012, 07:21 AM   #25
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Quote:
Originally Posted by Pixxt View Post
The EXT's are the least problematic general purpose filesystems in Linux, and better tested and a more bug free better track record than XFS, ReiserFS, JFS, BTRFS.
As people often tell me nowadays: prove it.

Ok, maybe I won't be that mean, how about some examples or articles ?

Honestly I think the bugs are due to bad decisions made by the devs, like when they first released ext4 and made the default 'data=writeback'. It was changed eventually, but it took time and data loss.
 
Old 10-25-2012, 12:26 PM   #26
qweasd
Member
 
Registered: May 2010
Posts: 436

Rep: Reputation: Disabled
Well, I am very happy with Pat's 3.2.29 everywhere but my laptop, where I have to run at least 3.3 on the account of Ivy Bridge. I can't pretend to understand this thread, but it looks like everything from 3.3 and up may be affected, so I guess I just have to not reboot until they fix it
 
Old 10-25-2012, 12:33 PM   #27
GazL
Senior Member
 
Registered: May 2008
Posts: 3,330

Original Poster
Rep: Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884
Now that more detail's have come out I don't think there is much cause for concern: unless you're system has a tendency not to shutdown cleanly for some reason.
 
Old 10-25-2012, 03:11 PM   #28
Pixxt
Member
 
Registered: May 2008
Distribution: Slackware, Debian,
Posts: 102

Rep: Reputation: 17
Quote:
Originally Posted by GazL View Post
Now that more detail's have come out I don't think there is much cause for concern: unless you're system has a tendency not to shutdown cleanly for some reason.
https://plus.google.com/117091380454...ts/Wcc5tMiCgq7

You're right!
 
Old 10-25-2012, 03:17 PM   #29
Martinus2u
Member
 
Registered: Apr 2010
Distribution: Slackware
Posts: 343

Rep: Reputation: 56
Quote:
Originally Posted by TobiSGD View Post
Has this error actually occurred to anyone?
I have lost a root file system on one machine last week. I can't say for certain it was the bug in question. It certainly followed precisely the pattern that is said to trigger the bug, but on the other hand the machine wasn't on 3.5.7 yet. I haven't had the time yet to assess the situation and salvage whatever I can, followed by a re-install.
 
Old 10-26-2012, 10:58 AM   #30
irgunII
Member
 
Registered: Jan 2012
Location: Directly above the center of the earth
Distribution: Slackware. There's something else?
Posts: 366

Rep: Reputation: 61
ReiserFS kicks ass. It's not let me down in 12 years of use. Started using it with SuSE 7.3 through openSUSE 11.3, then in Slackware 13.37 and now 14.0
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: EXT4 Data Corruption Bug Hits Stable Linux Kernels LXer Syndicated Linux News 1 10-24-2012 11:29 AM
[SOLVED] Having trouble with EXT4 on LVM on software RAID 5 (corruption) jostrus Ubuntu 1 07-29-2012 06:47 PM
Kernel bug causes EXT3 FS corruption? Gralgrathor Linux - General 6 10-24-2008 11:34 PM
LXer: Linux: Introducing The Data Corruption Bug LXer Syndicated Linux News 0 01-05-2007 01:24 AM
LXer: Linux: Data Corruption Bug Fixed LXer Syndicated Linux News 0 12-29-2006 02:03 PM


All times are GMT -5. The time now is 09:26 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration