Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
|
10-28-2012, 02:18 AM
|
#31
|
|
Member
Registered: Mar 2007
Posts: 212
Rep:
|
It seems that the bug has been found. https://lkml.org/lkml/2012/10/28/1
Kernel versions 3.4, 3.5, 3.6 have the bug. Kernels 3.2 and 3.3 are ok. Slackware-14.0 uses kernel 3.2.29 which is fine.
(Note that the bug was not added in any stable kernel iterations 3.4.x or 3.6.x. It was already in the original 3.4.)
Last edited by Petri Kaukasoina; 10-28-2012 at 04:21 AM.
Reason: Added clarification
|
|
|
3 members found this post helpful.
|
10-28-2012, 05:35 AM
|
#32
|
|
Senior Member
Registered: May 2008
Posts: 2,843
Original Poster
|
From another of Eric's posts in the thread linked to by Petri:
Quote:
|
So anyway, turning on journal_async_commit (notionally unsafe) enables journal_checksum (apparently broken).
|
So, turning on a potentially unsafe option, turns out to be actually unsafe, because it is broken!
I'll mark this as SOLVED. Anyone using sensible mount-options won't be hitting this.
|
|
|
|
10-28-2012, 09:08 AM
|
#33
|
|
Member
Registered: Dec 2010
Location: California, USA
Distribution: Slackware
Posts: 84
Rep:
|
Quote:
Originally Posted by irgunII
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
|
Be careful.
ReiserFS used to be good, but in recent kernels it has both momentary data corruption and performance problems. http://www.linuxquestions.org/questi...xt4-4175425294
These problems went away when I switched to ext4. Since not many people use or care about ReiserFS, its quality has gone down hill.
Ed
|
|
|
|
10-28-2012, 09:18 AM
|
#34
|
|
LQ Newbie
Registered: Apr 2006
Distribution: Slackware, Gentoo
Posts: 24
Rep:
|
Quote:
Originally Posted by EdGr
Be careful.
ReiserFS used to be good, but in recent kernels it has both momentary data corruption and performance problems. http://www.linuxquestions.org/questi...xt4-4175425294
These problems went away when I switched to ext4. Since not many people use or care about ReiserFS, its quality has gone down hill.
Ed
|
I liked RieserFS. It was fast. Or so it seemed. Somewhere along the way though I switched to ext4 for reasons I can't even remember.
|
|
|
|
02-19-2013, 10:39 AM
|
#35
|
|
Member
Registered: Jan 2012
Location: Directly above the center of the earth
Distribution: Slackware. What else is there?
Posts: 135
Rep:
|
ReiserFS is working fine on this system I have now (ASUS M5A97LE R2.0, AMD Athlon II X2 260, 4GB RAM) and on my old system (ASRock A770DE+, AMD Athlon II X2 250, 2GB RAM which I gave to my 73 year old mom as *her* old system was a P-3!). I've yet, in all these years of reiserFS use exclusively had a problem with it. I'll keep using it until the day it *does* start to screw up, but in thirteen years this month (so far) it hasn't and it is nice and stable and takes the beatings of power outages and brown-outs extremely well, imho.
|
|
|
|
02-19-2013, 10:35 PM
|
#36
|
|
Member
Registered: Mar 2007
Location: America
Distribution: Slackware 12.2
Posts: 140
Rep:
|
Quote:
Originally Posted by irgunII
ReiserFS is working fine on this system I have now (ASUS M5A97LE R2.0, AMD Athlon II X2 260, 4GB RAM) and on my old system (ASRock A770DE+, AMD Athlon II X2 250, 2GB RAM which I gave to my 73 year old mom as *her* old system was a P-3!). I've yet, in all these years of reiserFS use exclusively had a problem with it. I'll keep using it until the day it *does* start to screw up, but in thirteen years this month (so far) it hasn't and it is nice and stable and takes the beatings of power outages and brown-outs extremely well, imho.
|
I never had any issues with it either.
I've used it on External Drives quite a bit. Never lost data.
Even on crap hardware with dying controllers, it recovered.
I'd use it before I'd ever go back to NTFS.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 02:00 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|