Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Go to google and search for file system x and corruption or problems and try to find one where nothing shows up.
Still not convincing. I repeat: Are you trying to say all filesystems are equally prone to corruption? Sorry, but you sound like a member of reiser religious sect with hurt feelings. Not rational at all.
Funny..
Somebody modified the wikipedia page today. A lot of things have gone without even an explanation..
Quote:
Be careful using anything or any advice from wikipedia
Quote:
Getting reliable info from wikipedia is pretty much the same as military intelligence.
While I agree about the relevance of wikipedia, when the article explains features (it is a feature, not a problem..) by linking to the homepage of the project (sgi), I think it can't be wrong.
Quote:
Originally Posted by oss.sgi.com
So if the writes never make it to the physical disk, then the ordering is violated and the log and metadata can be lost, resulting in filesystem corruption.
It's funny how this subject always goes to an emotionnal state...
Still not convincing. I repeat: Are you trying to say all filesystems are equally prone to corruption? Sorry, but you sound like a member of reiser religious sect with hurt feelings. Not rational at all.
Hehe - I don't even use reiser at the moment and I couldn't care less about it.
See I am not the kind of guy that thinks based on what I use or not things are the greatest stuff on earth or junk.
I thought it was abundantly clear from my post that all file systems can get screwed up (that includes reiser - you do know what all means right?).
Do you even read posts before continuing your little xfs crusade?
Quote:
Originally Posted by me
So what? I had data corruption with ext2,jfs,xfs and reiser4 - not completely unexpected.
Never had a problem with reiser3 but that could also hit any time.
Looks more like you are the religious guy.
Last edited by crashmeister; 06-19-2007 at 11:35 AM.
Please, post #28 was the last sensible post here. admmoon, thank you for posting back, hope you post again when same computers suffer from corruption with ext3, or anything else happens worth mentioning on this topic.
--
Never argue with idiots, they tear you down into their level and then beat with experience.
Still not convincing. I repeat: Are you trying to say all filesystems are equally prone to corruption? Sorry, but you sound like a member of reiser religious sect with hurt feelings. Not rational at all.
What you are talking about - you yourself attacking people personally and after that becoming an moderator h.c. ?
To add what admmoon stated, wikipedia is a quick and dirty site.
Quote:
Yes I understand. I see that you are using 2.6.16 of the kernel.
My experience:When I was trying XFS, I was using a testing distro (bleeding edge) for development.
And, in kernel 2.6.17 (which I installed the same day as the release), an important regression appeared in XFS. At this time, the default tools to repair xfs did not do their job on my system. I was left with an unusuable disk until the bug was corrected/documented
This was too much for me: The above reasons in my other posts + this bug convinced me that XFS is not for my desktop PC and the use I make about it. Also my benchmarks were probably wrong because I noticed not a single performance increase but the opposite (due to intensive cpu usage and the process using the files not using the cpu enough)
I would like to try it again for my /var (some dir contains +1000 files) but I am just too scared that I loose again some files during kernel lockup/powerfail.
For any unstable project, data have to be backed up or else you will lose data. Using XFS for several thousands of files is ok. I still do not experience file corruption during power failure or during kernel lockup. I use ECC memory to minimize data corruption. In the past, ECC memory is included in every chipset. Now ECC is sparingly included and this creates problems when using several gigabytes of RAM. I recommend upgrade to ECC memory if the chipset supports it. If it does not support it, there is a high chance of data corruption. During development, ECC memory is mandatory because it filters out erratic problems that comes up when using NON-ECC.
I use my computer 8 to 16 hours a day, so XFS does get a lot of abuse. Yes, I have upgraded my computers to ECC memory. XFS did handle well when my hard drive had sector corruption a year ago.
I have been using reiserfs since suse 9.3, not once did I have data loss, even though I use it on a system without UPS and I have had several crashes due to unstable drivers (graphics card and SATA). That said, I'm considering switching to ext3, as the reiserfs development team is very small and seems to be unable to maintain the filesystem properly (ACLs and extended attributes are poorly implemented in reiserfs).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.