Slashdot Mirror


Which Partition Types Are Superior?

digitalmonkey2k1 writes: "I am currently planning on running an Apache web server and a small ftp on my pc. There are so many file systems that Linux can support now that I'm not certain what ones should be used for certain features. If anyone knows of a comparison list between them, somthing to give a pro/con method of deciding the best sort of configuration It would be greatly appreciated."

283 comments

  1. What's wrong with ext2? by Hercynium · · Score: 1

    It's never failed me! But if you want some sort of insurance, give ext3 a try. it's pretty schweet.

    Just DON'T even think about vfat or NTFS!

    --
    I'm done with sigs. Sigs are lame.
    1. Re:What's wrong with ext2? by Anonymous Coward · · Score: 0

      I know I'll get flamed for this, but I;ve had alot of good experiences with HFS+, yea yea, it's an Apple/Mac format, but it works well for large file sizes.

  2. Partition != File System by lkaos · · Score: 5, Insightful

    Therefore partition type is quite different from what file system to use.

    Besides, wasn't there just a story on Linux Advanced File Systems????

    There is no reason why use shouldn't use ReiserFS. Performs just as well (for the most part) as ext2 and will improve uptime by eliminating nasty fscks in the event of a failure.

    The more interesting question probably is what kernel should you be using????

    Kudos to story posters for having so many dups today. Really keeping us on our toes huh?

    --
    int func(int a);
    func((b += 3, b));
    1. Re:Partition != File System by Cheesy+Fool · · Score: 0

      > There is no reason why use shouldn't use > ReiserFS. Performs just as well (for the most > part) as ext2 and will improve uptime by > eliminating nasty fscks in the event of a > failure. It still corrupts data.

      --

      Hail to the king, baby!
    2. Re:Partition != File System by evildead · · Score: 2, Interesting
      reisferfs doesn't have backup and restore utilities, which can make like more than ... interesting.


      And no, tar is not an option, no matter what some Nameless Kernel Guru says. I've found that tar and cpio are awfully fragile and resource hoggish when it comes to backing up lots of data.

    3. Re:Partition != File System by LiENUS · · Score: 1

      evildead on the kernel mailing list someone reported that "dump" corrupts ext2 in the latest kernel whilst "tar" will not corrupt it so for now tar is the ONLY backup option for ext2

    4. Re:Partition != File System by Anonymous Coward · · Score: 0

      Heh, and the topic -- Programming?

    5. Re:Partition != File System by elflord · · Score: 1
      There is no reason why use shouldn't use ReiserFS. Performs just as well (for the most part) as ext2 and will improve uptime by eliminating nasty fscks in the event of a failure.

      ReiserFS is nice, but it hasn't been stable for very long. So you'd need a fairly recent kernel to deploy it safely. Of course, if you've patched for the ptrace exploit, you're already running a recent kernel anyway (-;

    6. Re:Partition != File System by MShook · · Score: 1

      Wich is true (http://lwn.net/2001/0503/a/lt-dump.php3): From: Linus Torvalds To: Neil Conway Subject: Re: [PATCH] SMP race in ext2 - metadata corruption. Date: Fri, 27 Apr 2001 09:59:46 -0700 (PDT) Cc: Kernel Mailing List [ linux-kernel added back as a cc ] On Fri, 27 Apr 2001, Neil Conway wrote: > > I'm surprised that dump is deprecated (by you at least ;-)). What to > use instead for backups on machines that can't umount disks regularly? Note that dump simply won't work reliably at all even in 2.4.x: the buffer cache and the page cache (where all the actual data is) are not coherent. This is only going to get even worse in 2.5.x, when the directories are moved into the page cache as well. So anybody who depends on "dump" getting backups right is already playing russian rulette with their backups. It's not at all guaranteed to get the right results - you may end up having stale data in the buffer cache that ends up being "backed up".

    7. Re:Partition != File System by MShook · · Score: 1

      So, I should have added that it is still a bad idea to backup an ext2 partition using dump/restore...

    8. Re:Partition != File System by big_hairy_mama · · Score: 1

      Does this apply to Ext3 as well? IIRC, Ext3 is just Ext2 with a journal added.

    9. Re:Partition != File System by Syberghost · · Score: 2

      There is no reason why use shouldn't use ReiserFS.

      This is insightful? I kinda figured a post had to be RIGHT to be insightful...

      There are several reasons not to use Reiser. There are lots of reasons to use it, as well, but you can't claim there are no reasons not to use it.

      One reason not to use Reiser might be that you're building a box that doesn't need it. A firewall with a very small hard drive and a good power backup, for instance.

      Another might be vendor support for your specific distribution. RedHat supports ext3 better currently, for instance.

      Just because their FAQ says there are no reasons doesn't mean there aren't any.

  3. This is becoming a FAQ by NevDull · · Score: 2, Offtopic

    Which filesystems to use for Linux is becoming far too big of a deal here on Slashdot. Can't we consider it a FAQ and let people do their own research?

    1. Re:This is becoming a FAQ by educated_foo · · Score: 1
      "Can't we consider this a FAQ and refuse to answer it?" Heh. It seems like a more appropriate response to point him to an actual "FAQ" (i.e. a document discussing the advantages and disadvantages of various Linux filesystems). I'm sure several such things exist, though since ext2 is good enough for me, I don't know where to find one.


      /s


      Moderators: why is this rated "insightful"?

  4. Short answer: by Matt2000 · · Score: 4, Insightful


    If you're looking to set up a small Apache and FTP for your friends, the short answer is probably: WHO CARES.

    Ext2 will be more than sufficient, and if you feel like it just download the latest Redhat (7.2) and get Ext3 default for free. It probably won't make much difference to you for this task unless you're in an area powered by thousands of gerbils on wheels who happen to get tired at the same time.

    --

    1. Re:Short answer: by snake_dad · · Score: 1
      unless you're in an area powered by thousands of gerbils on wheels who happen to get tired at the same time.

      I do not think that Afghanistan has internet access at this time... ;P

      --
      karma capped .sig seeking available Slashdot poster for long-term relationship.
    2. Re:Short answer: by Anonymous Coward · · Score: 0

      Keep in mind that if you install RH7.2 and use the default ext3 filesystem, you need to make sure that your future kernels all have ext3 patched in (or use Alan's kernels). If you install a vanilla kernel, the machine will not be able to mount the root filesystem when you reboot (since it doesn't know anything about ext3 filesystems). Major pain in the ass and good reason to stick with ext2 until Linux adds ext3 to the official kernel tree.

      Cheers,

      A coward

    3. Re:Short answer: by Knuckles · · Score: 2, Insightful
      if you install RH7.2 and use the default ext3 filesystem, you need to make sure that your future kernels all have ext3 patched in

      If you install a vanilla kernel, the machine will not be able to mount the root filesystem when you reboot (since it doesn't know anything about ext3 filesystems).

      ext3 filesystems can be mounted by ext2 kernels as long as the fs was cleanly unmounted. (Doesn't help you after a crash, though, there you're right) That's the nice thing aout ext3. That and conversion to ext3 on the fly. And that it claims to be as fast or faster than ext2

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    4. Re:Short answer: by Anonymous Coward · · Score: 0

      That's hardly FUD! The guy just didn't realise that you could do that. XFS/Reiser/JFS DO have the problem he mentioned though, so it's an understandable error.

      I think 90% of the posters here don't even know what "FUD" or "zealot" means anymore, they just label people and posts with it because they disagree.

    5. Re:Short answer: by Spacelord · · Score: 2, Informative

      Why even go as far as downloading a specific distro for it?

      I converted my slackware 8.0 system to ext3 in about 30 minutes. It's as simple as compiling a kernel with ext3 support, run tune2fs -j -Jsize=10 /dev/hdax and changing the fs type to ext3 in etc/fstab. Piece of cake...

    6. Re:Short answer: by Anonymous Coward · · Score: 0

      Internet (and computers) are banned by the talibans... so no, Afganistan probaly doesn't have an Internet connection....

    7. Re:Short answer: by Gendou · · Score: 3, Informative

      You're a real bright one, aren't you? "Didn't realize"? XFS, ReiserFS, and JFS are different filesystems; they're not ext2. Ext3 is ext2, but with a journal file added and journaling turned on. They're the same filesystem. It's even a bit disingenuous (though still correct) to say "Ext2 systems can mount ext3 filesystems," because there's no such thing as an ext3 filesystem -- just an ext2 filesystem that can, when mounted by the right kernel, support journaling.

      I don't really even know why someone would want to use ext3 anyway. Unless they've made some serious improvements in the past few months, the filesystem still writes at 50% the speed of ext2 (since all data is written twice). The only thing it has going for it is its interoperability with ext2, but that's really a perfidious "feature": systems that don't need journaling should just use ext2 to avoid the massive performance hit, and systems that do need journaling (namely, servers) have no reason to have their journaling filesystems compatible with ext2, and should use one of the high-performance journaling FS's.

    8. Re:Short answer: by Anonymous Coward · · Score: 0

      Because, if one can't choose a file system, they prob. don't kow where to start with a kernel compile. You might also note that he stated he was _planning_ an apache server - so it's doubtfull that there's an installation to convert.

    9. Re:Short answer: by ThatComputerGuy · · Score: 1

      They used to, but the Taliban banned it. No damn surprise there.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    10. Re:Short answer: by Anonymous Coward · · Score: 1, Interesting
      Here's a real story from my personal experience. I've used ext2 for many years without trouble. I've used reiserfs for about a 1.3 years mostly without trouble. The only real problem with reiserfs is that if you are using a disk that develops bad blocks, there is no graceful way to continue using that disk. Ext2 allows you to map out bad blocks, whereas reiserfs does not have a graceful way to do this.

      When one of my reiserfs partitions developed bad blocks, I had to use a low-level scsi reformat utility to fix the disk, and then reinstall. With ext2 you don't have to take that kind of dramatic action. You can easily inform the ext2 file system where the bad blocks are, and it will map them as unusable. I love the reiserfs, and it works well, but its userland utilities are not as rich or as flexible as ext2. As time goes on, this will change. However, at present, the inability of reiserfs to handle bad blocks gracefully could be something that might bite you if your hardware ever becomes flakey.

    11. Re:Short answer: by Clowning · · Score: 1

      All data is not written twice (your partitions don't hold half as much). Each file would have to be REALLY small (roughly equal to the size of the journal entry) to cause the equivalent of 2x the data to be recorded. I honestly don't know the average size of each journal transaction but I have trouble imagining it to be anything substantial. Not surprisingly, the write penalty is not often discernable. The tasks the original poster mentioned are more read dependent anyway.

      A non-negotialble benifit is the ease of making an ext3 partition (either from scratch or especially from and existing ext2 partition).

    12. Re:Short answer: by Anonymous Coward · · Score: 0

      Maybe the stupid fucker should know what the fuck he is talking about instead of talking out of his asshole.

    13. Re:Short answer: by MSG · · Score: 2

      "Didn't realize"?

      Not everyone realizes that the changes made to ext2 to add the journal are backward compatible. Don't be a dick.

      Also, the point he makes about the root filesystem may not be 100% accurate, but the problem *will* arise if you have more than one partition. That is, you might be able to get / to mount when you reboot, but when the init scripts try to mount /home, 'mount' will complain that ext3 is an unknown fs and fail to mount the filesystem. Other mounts could be far more catastrophic, like /usr or /var.

      the filesystem still writes at 50% the speed of ext2 (since all data is written twice).

      Not true. Only one of the journaling modes does this, and it's not the default. The default mode only writes fs data twice, and is usually much faster, since it optimizes drive head motion by ordering the writes.

      - It is better to remain silent and be thought a fool, than to open your mouth and remove all doubt.

    14. Re:Short answer: by ComputerSlicer23 · · Score: 1
      Actually it is my understanding that only the meta data is actually journaled. That is directory entires permissions, stuff about the structure of the filesystem, not the data. As far as I know, none of the current filesystems do full blown journaling because they would be 50% as fast. Actually because of all the drive seeks it would probably be even slower then that. If you really want high performance journaling it takes two disks, one to journal to, and one to write the actual filesystem too. Just like a good database would. I remember reading that being able to move the journal off to a seperate disk (possibly using one journal for serval filesystems?) was on the wish list for ext3. Personally I use ReiserFS. If Linus and crew sign off on it, I will try it.

      kirby

    15. Re:Short answer: by mrm677 · · Score: 1

      You're real bright too. Ever heard of backwards compatibility? I suppose you never considered why our microprocessors (PIII, Athlon) have 40 million transistors to accomplish the same thing as a PowerPC, or Alpha EV6 which have a quarter as many transistors.

      Not everybody has time to convert their *data* to a different file system. But hobbyists like you and myself probably don't have important data anyways.

    16. Re:Short answer: by ceswiedler · · Score: 4, Informative

      All data is NOT WRITTEN TWICE. RAID is a solution for replicating data. Journalling file systems replicate meta-data, which is the information ABOUT a file, such as its name and where it's stored on disk. They eliminate the need for fsck, which will not recover lost data either. Before you bash it, understand it.

    17. Re:Short answer: by unitron · · Score: 2
      That new Slashcode thingy that shows where links lead to makes it look like you said that the Taliban banned slashdot.org, which would certainly come as no surprise.

      Come to think of it, maybe it was a look at Slashdot that lead them to ban the entire internet.

      --

      I see even classic Slashdot is now pretty much unusable on dial up anymore.

    18. Re:Short answer: by Anonymous Coward · · Score: 0

      My comment is not really related to the fs, but i just wanted to point out that P3 and athlon having more transistors then PowerPC and Alpha has nothing to do with backward compatibility. It's because intel & amd have are CISC CPU while alpha and ppc are RISC CPU.. Two completely different architecture that explains the difference in the number of transistors. It has nothing to do with backward compatibilty..

    19. Re:Short answer: by mrm677 · · Score: 1

      well you just hit the point! The P3 and Athlon convert the CISC instructions to internal RISC-like "micro-ops". If the x86 instruction set would have been RISC in the first place, they would not have to spend 10,000,000 transistors to do the conversion. Hence they needed to do that because of BACKWARDS COMPATIBILITY! They couldn't just dump the instruction set because of backwards compatibility. Just like dozens of System Admins who cannot and will not reformat their partitions to a different FS. They will go to Ext3 because of the easy upgrade.

  5. Get a journaled FS by chrysalis · · Score: 5, Interesting

    XFS, ReiserFS, JFS or EXT3. Get a journaled FS. The reason is that as long as your system is up and running, having a fs like ext2 is no problem. But if you ever have crashes, long fsck (that something fail) means downtime. And for production servers, this is definitely something to avoid.
    XFS and ReiserFS are the more mature fs IMHO (on Linux) . I run EXT3 on systems that were previously running EXT2, because it's easy to upgrade. But I had some troubles with EXT3 not so long ago (corrupted files during a compilation, not even after a crash) .
    ReiserFS is the best if you have a lot of small files. Both for performance and space. XFS is believed to be better for large files.
    Also, if you need performance, FS is one thing, but software is another thing. Apache is probably the slowest web server out there (although very powerful (altough less than Roxen and Caudium :)) .
    Running Zeus, Tux or (for static content) WebFS will give you a huge performance increase, even on a slow filesystem.

    --
    {{.sig}}
    1. Re:Get a journaled FS by Anonymous Coward · · Score: 0

      XFS is a really great filesystem, but it's unfortunate that it will not be making it's way into the main kernel tree untill 2.5. The patches work pretty good, and debian_xfs is nice too, but with every kernel iteration, who wants to constantly patch? Sure, it might add a fair chunk to the kernel tarballs (or bzipballs, but let's make this sucker an option in a default kernel compile sometime soon!

    2. Re:Get a journaled FS by chrysalis · · Score: 2

      Another important point : XFS doesn't work with -ac kernel tree.
      However, productions servers are usually not updated every day (especially the kernel), so XFS with a working kernel is ok.
      But for workstations, ReiserFS may be a better choice, as it's in the kernel.

      --
      {{.sig}}
    3. Re:Get a journaled FS by ptomblin · · Score: 2

      Apache is probably the slowest web server out there

      It's plenty fast enough if you connection to your web "customers" is through a T-3 or smaller - it will pump out data, even from a mod_perl script, fast enough to flood the link. I've never put it on a faster link so I don't know how much faster a link it will flood.

      --
      The next Cmdr Taco duplicate will be ready soon, but subscribers can beat the rush and see it early!
    4. Re:Get a journaled FS by educated_foo · · Score: 1
      Why journal? He's serving content, so the filesystem will be mostly read-only. He's presumably not doing anything mission-critical, so an extra 10-minute fsck on (hopefully infrequent) reboots is not a big deal; if the system's staying up for ~100 days at a time, this is almost a total non-issue.


      /s

    5. Re:Get a journaled FS by Florian+Weimer · · Score: 1

      If the file system checks are in the 10 minute range, this is no problem, but if he's serving a couple of hundred gigabytes, this wouldn't be the case.

      In any case, if the file system is not that large and you want a solution that simply works, use ext2. All journaling file systems are not stable yet or lack essential tools (such as dump/restore or working fsck for real emergencies) or both. Of course, running some advanced file system is interesting in itself, so you might want to try one of them even if you don't need it, strictly speaking.

    6. Re:Get a journaled FS by Florian+Weimer · · Score: 1

      There are still reports that reiserfsck doesn't work as desired, only as specified. (It succeeds in putting the file system in a well-defined state, but alas, sometimes, all files are gone.) However, ReiserFS is in the official tree, so it gets most testing, and it directly follows other kernel changes, so the kernel component should work fairly reliably.

      XFS seems to have more mature userland tools (file system check, dump/restore). However, the XFS developers have a hard time tracking the mainline kernel, so if you want to get all those security fixes, you have to use their CVS version which gets less testing and is by no means an official version.

    7. Re:Get a journaled FS by captaineo · · Score: 2, Informative
      If you are using ReiserFS be aware that it does not journal file data, only filesystem metadata - i.e. after a crash your directory tree will always be intact, but files that were open during the crash can and will often have junk or misplaced data written to them.

      It is for this reason that I'm switching my machines to ext3. IMHO corrupted files after a crash are just as intolerable as a corrupted filesystem. (ext3 does have a reiserfs-like metadata-only journaling mode, but by default it journals everything - at a small performance cost of course).

    8. Re:Get a journaled FS by swordgeek · · Score: 2

      Fair points, but consider this:

      Why not journal? What could you possibly lose by running a filesystem that protects the integrity of your data better, and runs faster?

      As an aside, if he's exclusively serving data out, then the filesystem should be explicitly mounted read-only. Security and safety all at once!

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
    9. Re:Get a journaled FS by educated_foo · · Score: 1

      From what I understand, there's absolutely no way for journaling to buy you anything for mostly static data. So it comes down to luck and the fs's ability to cluster data. I am guessing that a filesystem that's been around for awhile would do better at this than a brand new one because it has had more time to be tuned, but I could be wrong about this (e.g. Reiser vs. flat directories when you have lots of files in one dir.).

      Another way to look at it is "disks are cheap and Linux has software RAID".

      /s

    10. Re:Get a journaled FS by Anonymous Coward · · Score: 0

      AFAIK you can tell resierfs to journal everything, but then it's almost as slow as ext3 in full-journal mode.

    11. Re:Get a journaled FS by mj6798 · · Score: 2

      That's true also of IBM's JFS, and probably XFS. Microsoft's NTFS makes even fewer guarantees. Journalling data is very slow and usually unnecessary.

    12. Re:Get a journaled FS by be-fan · · Score: 2

      Its really easy to track the XFS tree on a workstation too. I have a little script that automatically gets the CVS sources off the SGI website. I tend to get the Pre kernels (running 2.4.14-pre3 right now) but it works OK so far.

      --
      A deep unwavering belief is a sure sign you're missing something...
    13. Re:Get a journaled FS by Bryce · · Score: 3, Informative

      Here's a report on performance of some of these file systems: http://www.osdl.org/reports/journal_fs/. Obviously, performance is only one factor to consider when choosing a file system, so YMMV.

    14. Re:Get a journaled FS by mr3038 · · Score: 2
      corrupted files after a crash are just as intolerable as a corrupted filesystem.

      But journaling data doesn't get you too far if the programs you use aren't clever enough. Far too often an editor replaces file during saving instead of first writing a new one, after that removing old one and renaming new file to old filename. If your editor doesn't do this you're pretty much fscked up whether or not your filesystem supports journaling of data or not.

      On the other hand if you're editing big file the feature that editor replaces the file is must because you might not have enough disk space or quota to store it twice. The same applies for databases and stuff that needs to keep files open for acceptable performance. If an editor does write changes to new file first and only after that removes old file and still data is missing after crash it's simply unacceptable. There should be very few cases where data journaling actually helps.

      --
      _________________________
      Spelling and grammar mistakes left as an exercise for the reader.
    15. Re:Get a journaled FS by Anonymous Coward · · Score: 0

      ive never had a problen with text data... just restore the buffer file... ive lost one keystroke, maybe. admitidly, i dont do enough work out-side text to have had experenced any problems

      --oninoshiko, of the ban XP from the internet campain

    16. Re:Get a journaled FS by mr3038 · · Score: 1
      Here's a report on performance...

      From the link: "The target storage subsystem is a 10-drive RAID-1 array of 169 GB that is connected via a Qlogic IPS2200 fibre channel controller."

      Not exactly the system I'm using... I have to admit that ext2 seems to be pretty fast with that kind of hardware.

      --
      _________________________
      Spelling and grammar mistakes left as an exercise for the reader.
    17. Re:Get a journaled FS by Zurk · · Score: 1

      XFS uses genric functionality which 2.4 doesnt have but 2.5 will. thats one reason its not part of the stable kernel. i'd vote XFS anytime tho -- wish they had it backported to 2.2.20 (the only kernel i trust)

    18. Re:Get a journaled FS by piranha(jpl) · · Score: 1
      > Get a journaled FS. The reason is that as long as your system is up and running, having a fs like ext2 is no problem. But if you ever have crashes, long fsck (that something fail) means downtime.

      Well, my company has a very production Mandrake 7.1 box running ReiserFS. This box went down unexpectedly due to a shot CPU fan, and I had to try getting the system up as fast as possible. It booted, and reiserfsck worked its five-second magic as expected, and the system worked for all of about 20 seconds, until a fatal filesystem error popped up on the console (forgot what it was exactly) and I had to reboot into single-user mode to try to fix the problem. On a couple of the filesystems, reiserfsck told me that I needed to use the --rebuild-tree option, which it said was a somewhat risky thing to do, and that I should back up the filesystem I was going to use it on. So I did. That took about 10 minutes. When I actually ran reiserfsck --rebuild-tree, it took at least 15 or 20 minutes to complete.

      In the end, reiserfs costed at least half an hour of downtime on a production box, but the backup I made wasn't needed, as there appeared to be no lost files. To be fair, the kernel was 2.2.15-4mdk, so the implementation is probably a bit dated. This post is just meant to serve as a reminder that not all FS implementations are years mature, and in some cases you may run into little glitches. That aside, reiserfs is great.

    19. Re:Get a journaled FS by izzertaq · · Score: 1

      ext3 doesn't journal everything by default. Rather, it makes the guarantee that data will reach the disk before metadata, which for most applications is Good Enough(tm) to guarantee data integrity after a crash.

    20. Re:Get a journaled FS by cmclean · · Score: 1
      ...with -ac kernel tree.

      What?!? AC's have their own kernel tree now?
      Sheesh...

      cmclean

      --
      "Any similarity between the hooting of a million eager monkeys and Slashdot is purely coincidental." -THEFLASHMAN
    21. Re:Get a journaled FS by Alphix · · Score: 1

      Not quite true.

      XFS uses functionality that is written specifically for XFS that makes changes in many kernel subsystems (which is a big reason why it's not in 2.4).

      The plan is to add that functionality in a "generic" way to those subsystems (in 2.5). This is to make sure that all filesystems (that "want" to) can use the benefits of the new functionality.

    22. Re:Get a journaled FS by gorilla · · Score: 2
      Far too often an editor replaces file during saving instead of first writing a new one, after that removing old one and renaming new file to old filename.

      No, this is the correct way to update files. If you follow your instructions, then the permissions, any hard links will be lost.

    23. Re:Get a journaled FS by Anonymous Coward · · Score: 0
      Bah. Journalling FSes are not a panacea. Personally I find data loss more abhorrent than downtime and I'm willing to sit through a few minutes' fscking just to make sure that I haven't corrupted any of the data in my files (and not just that the file metadata is okay).

      Having had a bit of experience with ReiserFS at least, I can say that just because a filesystem is a journalling filesystem doesn't mean it's better for your data. Linux tends to mount all filesystems async by default, so if you have a massive powerfailure, even with a journalling filesystem, you're likely to have lots of corrupted data. Sure, ReiserFS makes sure that the filesystem metadata is all OK, but that is all.

      Sure, you can sync mount your journalling filesystem but guess what? Now it's slower than many non-journalling filesystems that are sync mounted.

      This is why for really important stuff, I still don't use Linux. I love Linux as a workstation and as a testbed machine without any really important data on it, but if I want to be reasonably sure that a power failure isn't going to totally screw the data in my files, I use one of the BSDs which sync mount their filesystems by default and use the time-tested and mother-approved UFS (a.k.a. FFS) filesystem. Add in Kirk McCusick's Soft Update extensions and things are nearly as fast as ext2 without losing too much in terms of data integrity.

      Just in my own anecdotal experience, I've had considerably fewer problems with data loss on my OpenBSD and FreeBSD servers than any Linux server I've ever used (unless it mounted it's filesystems synchronously, in which case filesystem speed sucked big cock) through the same kinds of circumstances.

      Yeah, I'll use Linux. I just won't store anything really important on a Linux box anymore. (Not without backing everything up >= daily, anyway.)

  6. Which I would choose by 1stflight · · Score: 2, Interesting

    For Linux, I've got to say that with the right hardware (fast drives) any of the newer journaling filesystems would be excellent. Why?
    1. Data protection - the journaling systems Reiserfs, Ext3, XFS; etc offer far better and faster recovery than Ext2 does
    2. Configurable, though I've never found a need to do it, you can set the block sizes in Ext2 and 3 to optimize it for larger files or smaller ones

    What to stay away from fat/vfat/fat32. Why?
    1. No security, period

    *clink, clink* just my two cents..

    1. Re:Which I would choose by lkaos · · Score: 1

      2. Configurable, though I've never found a need to do it, you can set the block sizes in Ext2 and 3 to optimize it for larger files or smaller ones

      This is less a performance enhancement and more a hack because of the finite amount of available inodes in ext filesystems.

      ReiserFS dynamically allocates inodes so such as hack is unnecessary. ext filesystems are no more configurable than ReiserFS.

      In fact, one can make very few arguments for using ext over ReiserFS. As reiser matures, I don't think there will be any reason to use ext2.

      --
      int func(int a);
      func((b += 3, b));
  7. File system is half the disk story by Anonymous Coward · · Score: 2, Insightful

    I can't address your question directly, but don't forget that things like block size can have just as large an effect on file system performance as the vhoice of FS itself.

    1. Re:File system is half the disk story by Anonymous Coward · · Score: 0

      ain't it too bad that you can't use a block size greater than 4k anywhere? At least we have source to fix those "features".

  8. ReiserFS by abcdefg23562 · · Score: 2, Interesting

    I would use ReiserFS, it has always worked good for me.
    The best part is the journalling, if your machine with a 50 gig drive loses power and reboots, you do not have to go through a lengthy fsck, this would greatly decrease the boot time of your server.

  9. Ext3 with standard dos-type partitions by 1010011010 · · Score: 5, Informative

    DOS-type partitions are the most common on PCs, the most expected, and the easiest to deal with.

    Ext3 is basically ext2 with journalling. It performs better than Ext2, though. In a pinch you can always mount it as ext2.

    You're not running anything exotic. Stick with the standards.

    --
    Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    1. Re:Ext3 with standard dos-type partitions by lkaos · · Score: 1

      Ah, no. Linux native partitions (83) if you want to support ext2 or any other fs.

      DOS-type (6, e) partions will not support a linux filesystem.

      I imagine your not referring to FAT32 (b, c) since that is in no way a DOS partition whereas FAT16 was just an extension of the original DOS filesystem much like the PE executable is just an extension of the MZ executable.

      --
      int func(int a);
      func((b += 3, b));
    2. Re:Ext3 with standard dos-type partitions by 1010011010 · · Score: 2

      Ah, no. DOS-type partitions are the standard 4-primary, or less than 4 primary plus one or more "extended" partitions with "logical drives" (paritions) in them. These partitions may be marked as being MSDOS, NTFS, QNX or whatever. But they are still DOS-style partitions. I.e., what you get by partitioning your disk with DOS fdisk.

      In contrast, you can have BSD-style disk slices or some other partitioning scheme that bears no relation to what DOS uses.

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    3. Re:Ext3 with standard dos-type partitions by dougmc · · Score: 2
      I think you misunderstood the post you're replying to.

      He was suggesting using the standard DOS partitioning scheme (you know -- up to 4 primary partitions, one of which can be turned into a logical/extended partition for more partitions) with an ext2 filesystem put onto these partitions.

      There are other options -- you could just mke2fs /dev/hda if you wanted to, and you could use one of the other available partitioning schemes if you wanted -- but using the standard DOS scheme probably makes the most sense for most people.

    4. Re:Ext3 with standard dos-type partitions by Anonymous Coward · · Score: 0

      My understanding was that the partitioning scheme was invented for the IBM PC and not DOS in particular (the PC shipped with a choice of DOS, CP/M-86, and the UCSD Pascal OS thing).

  10. Reiserfs, if you've got good hardware by Anonymous Coward · · Score: 2, Informative

    I like Reiserfs the best. That's to say: it is fast, is a journal filesystem and it's fast.

    As to reliability: if you've got good hardware, there shouldn't be any troubles at all. I for one, don't have good hardware. /usr/local/mp3 resides on a partition that seems to have some errors on the disk. I lost several mp3s before I realized that the disk was screwed up. Nope, you don't get any early warnings from reiserfs.

    Their repair tools suck, by the way.

    So why do I keep using it? It's fast, is suse's default filesystem and it's fast.

  11. Some other questions.... by rweir · · Score: 0, Troll

    Which editor is better, vi or Emacs?

    How is Linux better than Windows?

    Why should I choose Linux over *BSD?

    (For the humour impaired: it's a joke, goddamit, and not a very good one at that).

    1. Re:Some other questions.... by Anonymous Coward · · Score: 0

      the answers are: yes, yes and yes!

    2. Re:Some other questions.... by IpalindromeI · · Score: 0, Flamebait

      1. Don't use vi, it's old and outdated. For a better editor, use vim. For a better do-everything-you-can-think-of-less-well-than-stan dalone-apps-with-editing-thrown-in, use Emacs.
      2. Linux is better than Windows because the name isn't just feature it's built on. (Oh look, apps run in "windows" now. Let's call this operating system Windows.) If it was, Linux would probably have a name like Stability OS or something. (Hey, there's a great idea for a new OS name!)
      3. I don't know. I've never had contact with *BSD. But BSD's mascot is definitely cooler.

      --

      --
      Promoting critical thinking since 1994.
  12. NO, NO, NO! by ajuda · · Score: 2, Insightful
    Your question is like a lot of the following:

    Which is the best car?

    Who is the best actor?

    Where is the best place to live?

    None of these questions can be answered without saying "It depends" and neither can yours. Very rarely is anything better than everything else is every single way.

    1. Re:NO, NO, NO! by Anonymous Coward · · Score: 0

      1929 Royals Royce Silver Ghost
      Laurance Oliver
      Lyford Cay, New Providence (Bahammas)

    2. Re:NO, NO, NO! by Anonymous Coward · · Score: 0

      Yes, but he gives his situation for use, he didn't just ask "which FS is best".

    3. Re:NO, NO, NO! by Anonymous Coward · · Score: 0
      "Where is the best place to live?"


      Lesbos, Greece.

    4. Re:NO, NO, NO! by MaynardJ · · Score: 1

      He's asking for a comparison list of features between the various filesystems, not "which one is best". Read the post again.

    5. Re:NO, NO, NO! by IpalindromeI · · Score: 2, Insightful

      Very rarely is anything better than everything else is every single way.

      Watermelon is better than every other fruit in every single way.

      --

      --
      Promoting critical thinking since 1994.
    6. Re:NO, NO, NO! by Verence · · Score: 1

      You didn't even read his question.

      He was asking for a pro/con list- not a definite 'which is the best'

      The poster obviously wanted a list of features and detriments- or a place to find them. Truthfully did not want to know if the Intrepid was better than the Taurus (don't even know if thats a good example.)

      --

      ... that's all i wrote...
    7. Re:NO, NO, NO! by Anonymous Coward · · Score: 0

      -Dodge Viper GTS
      -Harrison Ford
      -Hanover, Indiana

    8. Re:NO, NO, NO! by Anonymous Coward · · Score: 0

      except for kiwi.

    9. Re:NO, NO, NO! by Anonymous Coward · · Score: 0

      Watermelon and kiwi are horrible.

      Only Apples are better than any other fruit in every single way.

    10. Re:NO, NO, NO! by Anonymous Coward · · Score: 0

      i know something that goes against your statement: SEX.

    11. Re:NO, NO, NO! by Siva · · Score: 1

      those of you instructing the author of this post to "read the question again" should perhaps read the title of the article again. if we assume (logically) that the title of the article is meant to be a few word summary of the theme of the article, then this poster is right on the money, IMHO.

      --Siva

      --

      Keyboard not found.
      Press F1 to continue.
    12. Re:NO, NO, NO! by Chandon+Seldon · · Score: 1

      Watermelon is better than every other fruit in every single way.

      I'm afraid it can't compete with the ease of use of a banana.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    13. Re:NO, NO, NO! by Anonymous Coward · · Score: 0

      Wrong. The pomegranate wipes the floor with any other fruit. One word: Grenadine. Mmmm mm!

      I like Shirley Temples.

    14. Re:NO, NO, NO! by Mad+Marlin · · Score: 1
      >> Watermelon is better than every other fruit in every single way.

      >I'm afraid it can't compete with the ease of use of a banana.

      Obvious solution: genetically engineer a watermelon in a container similar to a banana. Result: the Waternana!

    15. Re:NO, NO, NO! by Anonymous Coward · · Score: 0
      > read the title of the article again.

      Kinda like just reading the slashdot summary and skipping the linked article, then flaming the author of the linked article.

      But that of course never happens here...

    16. Re:NO, NO, NO! by Anonymous Coward · · Score: 0

      1) BMW M5
      2) Anyone but Keanu
      3) Vancouver, BC

    17. Re:NO, NO, NO! by unitron · · Score: 2
      "I'm afraid it can't compete with the ease of use of a banana."

      "Obvious solution: genetically engineer a watermelon in a container similar to a banana. Result: the Waternana!

      Or, depending upon what was meant by ease of use, the dildo-melon.

      --

      I see even classic Slashdot is now pretty much unusable on dial up anymore.

    18. Re:NO, NO, NO! by Anonymous Coward · · Score: 0

      Bugatti Veyron, Edward Norton, NYC. Any other questions?

    19. Re:NO, NO, NO! by laa · · Score: 1

      I totally agree (except for the last one - the best place to live is at home). I'd like to see a poll on which FS is the most used, but discussing the matter tends to lead into religous wars - and I think one jihad is enough for today.

      --
      Why does the kernel go through stable and then unstable forks? Can't it always be a stable build, like with Windows?
  13. ReiserFS has distinct advantages. by dbuttric · · Score: 5, Informative

    I use it for the document root of my webservers. It offers faster access to the files themselves, while having very good fault tolerance.

    I serve very few dynamic documents - I'm getting alot of milage out of small machines. My sites have a deep directory structure, with fairly few files in each. ReiserFS shines for this layout.

    I tested several different FS for this application, ReiserFS won for me.

    Oh yeah, the other benefit is the relative ease of install and upgrade.

  14. journalized fs by nilstar · · Score: 1

    If you are going to choose a Journalized FS, check out the benchmarks and see which ones best suit your need. For example if you need little writing, but lots of read access (eg, data warehouse)... or if you need lots of servlets constantly accessing/updating data... or if it is a simple web server... you should look at which Journalized FS is best for you via a look at the benchmarks/home pages for the appropriate FS.

    I personally use Reiser FS on my "home surfing/programming" machine... because of the extensive support (especially in certain distros).

    --
    ===> An eye for an eye makes everyone blind - MG
  15. My preferred partition type is... by mzito · · Score: 5, Funny

    83! It's easy to remember, simple, and comes default in 100% of linux distributions.

    Of course, there are those who are type 82 bigots. I can see how that's important, but with RAM prices so low these days....

    Matt

    --
    me@mzi.to
    1. Re:My preferred partition type is... by lkaos · · Score: 1

      Gotta have some 82... I don't care if you have a 1GB of memory. Swapping is so much fun!

      --
      int func(int a);
      func((b += 3, b));
    2. Re:My preferred partition type is... by TV-SET · · Score: 1

      RedHat 7.2 uses ext3 as a default. I am not sure though, which number assosiates with that, but my bet would be that it is not 83, therefor your statement about 100% of linux distributions is not true :)

      --
      Leonid Mamtchenkov ...i don't need your civil war...
    3. Re:My preferred partition type is... by mzito · · Score: 1

      Well, it was a joke - but yes, it does use 83 as its partition type.

      Matt

      --
      me@mzi.to
    4. Re:My preferred partition type is... by Anonymous Coward · · Score: 0
      RedHat 7.2 uses ext3 as a default. I am not sure though, which number assosiates with that, but my bet would be that it is not 83, therefor your statement about 100% of linux distributions is not true :)


      moron.

    5. Re:My preferred partition type is... by Da+Masta · · Score: 1

      Even thogh this is a joke, it does touch upon an important point that some replies apparently don't understand:

      Partition type is different from partition format. ReiserFS, XFS, ext2, ext3, JFS are all partition formats and are the filesystems used on the disk. Partition type is only a number in the partition table, and in their Linux incarnations, all the aforementioned filesystems use type 83, simply indicating that partition is meant for Linux. You can call a partition type 69, and still format it with ext2 for all that it matters.

    6. Re:My preferred partition type is... by mmontour · · Score: 3, Interesting

      It's nice to have some type 8e around too - Linux LVM. Logical volume management lets you do some cool things, like re-sizing your partitions with the data in place. You can add free space to a logical volume with reiserfs while it's "live", although you have to unmount the volume if you want to shrink it. *Very* handy when you don't know at install-time exactly how much space is going to be taken up by your /home, /usr, /var/log, etc.

      Of course the Amiga "RDB" partitioning scheme had its nice points too. Linux can read it, but I don't know if there are any Linux tools to create one.

    7. Re:My preferred partition type is... by Anonymous Coward · · Score: 0

      Well, the M68k version of linux fdisk can write Amiga RDB - it'd "just" be a matter of fixing endianness issues and recompiling..

    8. Re:My preferred partition type is... by Anonymous Coward · · Score: 0

      And to further confuse the issue - don't forget about partitioning schemes. Linux and MSOD both use the ancient MSDOS scheme, that even MS has moved away from in 2000 and XP. There are much better systems, many of which linux supports just fine, such as BSD slices and so on. (See the "advanced Partition selection" options in linux kernel build configuration)

    9. Re:My preferred partition type is... by TV-SET · · Score: 1

      Thanks... I've missed the point first time.

      --
      Leonid Mamtchenkov ...i don't need your civil war...
  16. Readonly by aXi · · Score: 0

    Just use ext2 in the readonly mode, remounting it to rw whenever you have to make changes. If a system crashes with an ext2 filesystem mounted read only, it will be clean. Further more it is more secure, people can not change your system withou loggin in. And if you need people to be able to write to certain directories, have filesystems mounted rw to those directories.
    A sample fstab:

    /dev/sdc1 / ext2 defaults 1 1
    /dev/sdc2 /home/ftp/ ext2 ro,defaults 1 1
    /dev/sdc1 /home/ftp/upload ext2 defaults 1 1
    etc

  17. ext stuff by Apreche · · Score: 2

    If you are running a big server with mad power you probably want ReiserFS. If you are running anything else you probably want ext3. You wont notice any difference between the two unless you are running a very large powerful web server with many visitors, like slashdot here. For you, just about any file system on the list will work.

    --
    The GeekNights podcast is going strong. Listen!
  18. My choices by secondsun · · Score: 2, Interesting

    I used ext2 about a year or so ago. I didn't mind the fscks (I only had a 4 GB drive) but 2 times it didn't work and I had to maunally fix some files. Then I got reiserfs and to this day I have had no troubles (short of a tree rebuild every few months just to improve speed).

    I did have a vfat drive (40 GB) that had a whole bunch of stuff from a when I used windows (98 SE then 2000 then XP) then I reinstalled and used it as a secondary drive. Worked for a few months until the partition table became corrupt, NOrton couldn't fix it and well here I am. (It is now a 40 GB reiser fs partition.)

    Secondsun

    --
    There is nothing wrong with being gay. It's getting caught where the trouble lies.
    1. Re:My choices by Anonymous Coward · · Score: 0

      how does one do "tree rebuilds" on reiserfs ?

  19. Shouldn't be a difficult choice by SumDeusExMachina · · Score: 2, Funny
    When choosing a filesystem, you want to build compatibility into your system, so that you can afford to change your mind later if you want to change the way you do things. With that in mind, I think you would be best off with using NTFS for your filesystem. Not only does it have advanced ACL support and built-in filesystem encryption (which is handy if you are the type to worry about security problems), but it also performs at a very advanced level, literally blowing away such "free" systems such as ext2.

    Best of all, you can fully utilize it under Linux as well as Windows 2000, so if you feel like you would be better off with developing under Windows, you wouldn't have to reformat your whole disk and lose data in the process. Benchmarks have consistently shown that it is an enterprise-class performer.

    Finally, you have to consider reliability in decisions such as these. NTFS just doesn't lose data, which is more than we can say of such "lossy" systems such as ReiserFS. Frankly, I can't even see why people put such "journaling" systems on production machines. All in all, you can't go wrong with NTFS.

    --

    Is your company running tools written by ma
    1. Re:Shouldn't be a difficult choice by Anonymous Coward · · Score: 0

      Unfortunately for your post, ReiserFS doesn't just lose data, either. And anyways, in my experience with NTFS, whenever Win2k freezes, more often than not I will end up with a corrupted filesystem that takes hours to check, when chkdsk doesn't even fix all the errors! What kind of filesystem is that?

    2. Re:Shouldn't be a difficult choice by DigitalGlass · · Score: 1

      I can see you havn't been reading anything on NTFS latley. Do you know what *usually(not always)* happens when you write to an NTFS partition under linux? .... things go wrong. The whole filesystem can get corrupted. ReiserFS or EXT3 would be the better of the choices in my humble oppinion.

    3. Re:Shouldn't be a difficult choice by LiENUS · · Score: 1

      uhhh this has to be a troll
      #1 ntfs doesnt work under linux
      #2 there are "free" systems that have ACLS (i believe XFS is one such)
      #3 ext2 supports encryption i believe
      and #4 NTFS is journaled i believe.

    4. Re:Shouldn't be a difficult choice by dvdeug · · Score: 2

      > Finally, you have to consider reliability in decisions such as these. NTFS just doesn't lose data

      Then why is the Linux write-drivers marked "dangerous" and "back up your NTFS volume first, because it will probably get damaged"[!!!]? Trying to run Linux off NTFS just sounds like a bad idea.

    5. Re:Shouldn't be a difficult choice by dvdeug · · Score: 1

      Oh, and BTW:

      I don't want any filesystem that can _literally_ blow away ext2. If it produces that much wind as to somehow get rid of a filesystem, it will probably damage the harddrive and other parts of the computer.

    6. Re:Shouldn't be a difficult choice by Anonymous Coward · · Score: 0

      That's true. NTFS = good under NT, but I wouldnt even think about it under Linux.

    7. Re:Shouldn't be a difficult choice by rutledjw · · Score: 1

      Are these morons part of some MS Grass-Roots marketing campaign? It seems like more and more that we're seeing posts which are pushing MS technology under the auspices of technical discussion

      Running an NTFS filesystem under Linux seems to redefine the limits of stupidity IMHO (and I AM humble! ;) ). You have ext3, RieserFS among others which offer some great features running on an OS which has very good stability (Linux), so what do you do? We'll go use a FS from EvilEmpire Inc and import some of their problems. I'm sure THAT will be high-quality!

      That's like breeding a chihuahua with a doberman. I don't know what will come out of such a union, and I doubt I want to...

      OK, I'll admit I'm a *nix snob, no bones about it, but please...

      --

      Computer Science is Applied Philosophy
    8. Re:Shouldn't be a difficult choice by Anonymous Coward · · Score: 0

      I thought Bill was banned from this site?! - NTFS, my a%s*!!!

    9. Re:Shouldn't be a difficult choice by ninewands · · Score: 1

      That's like breeding a chihuahua with a doberman. I don't know what will come out of such a union, and I doubt I want to...

      You'll get either a small dog with a dobie attitude (bad news, but tolerable) or a BIG doc with a Chihuahua attitude (I'm not even sure THAT would be safe to live with) ... ;-)

  20. Whats wrong with google? by Anonymous Coward · · Score: 1

    Whats wrong with google? Surely it is more appropriate to search for this kind of thing, instead of making it into another askslashdot.

    1. Re:Whats wrong with google? by damiam · · Score: 2, Informative

      Excellent point - a brief google search found this page, a summary of the performance of ext2, ext3, jfs, xfs, vfat, and reiserfs.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    2. Re:Whats wrong with google? by ninewands · · Score: 1

      ... found this page [zemris.fer.hr], a summary of the performance ...

      and I must say the side-by-side numbers make XFS look pretty good.

    3. Re:Whats wrong with google? by Anonymous Coward · · Score: 0

      I never heard of a goodle partition. Is this in mandrake? I can't find it at mandrake's site, or on my 8.0 disks. Is it strictly red hat's partition system?

  21. ACLs on ext2, ext3, xfs by trackzero · · Score: 5, Informative
    I administer a network of about 25 linux boxen used largely for file service. For such work, I must say that with 9,000 users and about 30 groups, I consisder ACLs a necessity. I've been using the "Bestbits" ext2 acl patch with great luck (acl.bestbits.at). I've heard that a cousin to this patch can be applied to ext3, but I haven't tried it yet. I'm drawn to XFS for its maturity, durability, and of course its ACL support.

    The XFS command line utilities seem to be less effective than the Bestbits patches & utils, and the Samba 2.2.1a support seems to be a bit off with its handling of recursive descents and inheritance. To be fair on both counts, I'm still learning the file system, and the problems could be all mine.

    I'd thought about ReiserFS, but I really need those ACLs.

    Just some thoughts. Any errors are all mine. Please feel free to correct. I have no pride.

    --
    "Laugh Quietly- tomorrow is your turn to be rong."
    1. Re:ACLs on ext2, ext3, xfs by Anonymous Coward · · Score: 0

      why isn't this modded up? Instead of the normal
      jackass shit most of the posts contained, this actually contained useful information.

    2. Re:ACLs on ext2, ext3, xfs by Anonymous Coward · · Score: 0

      It's modded up now, but it shouldn't be. The poster asked a question about running a small personal web server, and this answer contains information about "features" that may apply to a 9000 user organization, but are completely irrelevant to the question asked. -1 Offtopic would be fairer.

    3. Re:ACLs on ext2, ext3, xfs by Anonymous Coward · · Score: 0

      Look at this, is FS independent.
      I'm using whith reiser.

      http://trustees.sourceforge.net/

  22. ReiserFS is better. by chicobaud · · Score: 5, Informative

    This FS doesn't fragment file around partition space, major advantage if you install in hardware RAID. Fragmentation is a big problem for performance, so if it doesn't happen you have a good access time. I use ReiserFS on SuSE and Mandrake, it is fast/good, doesn't loose data and I tried the journaling by shutdonw bad my isntallation many times before a fresh install, never lost a single file, this amazed me since I dilike the fschk everytime maximal mount count and a forced unmounted FS situation happened.
    Try ReiserFS. Too bad RedHat 7.2 decide not to support ReiserFS, I will give up - with regreat - on RedHat.

    1. Re:ReiserFS is better. by essell · · Score: 1

      1) Nice try on the English, don't worry.. you'll get there!
      2) Just because RedHat doesn't implement ReiserFS "natively" does NOT mean you cannot use it, nor does it mean that RH "decided" not to support it. They simply chose a different journaling FS which, imho, works pretty well.

      Are there any other distributions that implement Reiser as default?

      --
      i swear my userid used to be lower.
    2. Re:ReiserFS is better. by tannhaus · · Score: 0

      Ummm...I'm loss here and I'm running Redhat 7.2. I installed it using ext2 partitions (still an option) and I'm about to switch to reiserfs. The reiserfsprogs rpm was included by default. It's not that you CAN'T install reiserfs (IIRC, I had it installed when i had redhat 6.2 which included NO journaling filesystems), but their installer doesn't include it. That's no biggie. I use several programs (kvirc, xv, etc) that their installer doesn't include.

      If anyone is wondering why I just installed redhat, actually I've been running it at home for 4 years. It's just that every once in a while I like to wipe everything but /home away and do a clean install...just to see what it's like. I have done upgrades in the past but sometimes my curiosity gets the best of me.

    3. Re:ReiserFS is better. by chicobaud · · Score: 1

      Your english needs improvement too (choose is not chose). Falas a minha língua, mas não sabes ladrar ?

      I mention RedHat 7.2 because they seem to avoid European stuff many times, after all ext3 is the same as ext2. ReiserFS is much faster when you don't want file fragmention. ext3 was not designed from ground up and looking for file access time as goald one.

    4. Re:ReiserFS is better. by Anonymous Coward · · Score: 0

      ummm.... sorry dude, his english looks fine.

      chose is the past-tense form of choose. i.e. they aren't still in the process of choosing their FS, they already did it.

    5. Re:ReiserFS is better. by Nau.dk · · Score: 1

      Choose is present, chose is past tense, both could be used in the sentence.

    6. Re:ReiserFS is better. by loopkin · · Score: 1

      /*
      * linux/fs/ext3/inode.c
      *
      * Copyright (C) 1992, 1993, 1994, 1995
      * Remy Card (card@masi.ibp.fr)
      * Laboratoire MASI - Institut Blaise Pascal
      * Universite Pierre et Marie Curie (Paris VI)

      hmm.. that seems pretty European to me, no ?
      RH avoided KDE for a while because of QT licensing problems.. they were slow on jumping back on the train afterwards and still remain GNOME oriented, but now KDE is supported (i guess this was the sense of ur European stuff..).

    7. Re:ReiserFS is better. by madenosine · · Score: 1

      Your first comment about his English was completely offtopic, first of all. Second, it is pretty obvious that you can add support for reiserfs, and format, but the fact is that it is harder to get reiserfs as the root filesystem in Red Hat 7.2, although you could obviously do it.

    8. Re:ReiserFS is better. by chicobaud · · Score: 1

      They avoided KDE for a while but got back on the train ... and now are avoiding ReiserFS for a while ... but will get back on the train ...

      I apolagize for my english and my comment on the chose not choose, I understand those are different and correct (era melhor que respondessem sobre o assunto).
      Sorry if it was off the topic.

      Still there is unnecessary difficulties to get up and running a RH 7.2 in ReiserFS (I idin't install a RH 7.2 yet) wich could have been avoided because Reiser is on the kernel allready.

      Never mind my english; plus, I like to type fast...

      And there is the fragmentation issue.

  23. PC partition types suck by bug1 · · Score: 1

    PC partition tables are a pile of crap, legacy crap going back 20 years, we only need LBA support and nothing else.

    Whats the go with 4 primary partitions, the nextended partitions, some OS's primary partitions have to overlap extended partitions, some they done, some you can only use 1 primary partition, some you can use them all.

    And having to reserve the whole first track, usually 32 sectors, just to put in about 170 bytes of data... what a waste.

    The extra space can be used by other disk externder type programs, but there is no standard way to reserve it or anything, its first in best dressed, use it at your own risk.

    And look at what it has to do, it just has to mark the start and end of a section of raw disk space, how difficult is it ?

    The format has just been butchered too much by too many people. But for practical reasons we are stuck with PC partition tables because of convenience for the masses.

    You could do a raw LVM partition.
    I like Acorn partition types (if thats the one im thinking of), nice and simple, only what you need.

  24. reiser fs by n3m6 · · Score: 0, Redundant

    i heard that reiser fs handles small sized files better than all the other current fs's .. small in size and large in number i mean.. good for webservers. where u get hundreds of under under 5k files ..

  25. Let's not confuse FS and Partition type by Anonymous Coward · · Score: 5, Informative

    The question asked for information about partitition schema, not file systems. And yet almost every post so far has been about file systems.

    IMHO, if you want a superior partition scheme, you should not use the linux system, which is identical in structure to the Microsoft DOS system. Instead, read about the BSD partition (and slice) system. See section 2.5.2 of the (new) 2d edition handbook:

    http://www.freebsd.org/doc/en_US.ISO8859-1/books/h andbook/install-steps.html

    In BSD, the Microsoft-Linux concept of partitions is preserved as "slices" that exist to hold collections of files systems. (In FreeBSD, you can man hier(8) to read more about this. Unlike linux, where every vendor puts things in /opt, /etc/, /usr/local, and so on, the BSD system is very rigid--there's even a man page about where things belong.)

    Another option in BSD is the use of what are called "dangerously dedicated" system where the entire disk becomes one slides, with no other partition. Read more about this in the handbook. There's even information about working with different flavors of partition types.

    I suppose to give 'equal time' we should give a link to the Microsoft/Linux partition scheme, so here one is:

    http://www.redhat.com/docs/manuals/linux/RHL-7-Man ual/ref-guide/ch-partitions.html

    FYI-- here's some news you won't see on /.'s main page: The FreeBSD handbook (first link above) was just (48 hours ago) released in its second edition. This is a significant documentation change, and all the daemons are celebrating. Join us!

    1. Re:Let's not confuse FS and Partition type by bug1 · · Score: 1

      bsd partitions have a lot of cruft in them, there are fields for storing all sorts of irrelivant information.

      (e.g fields extracted from http://www.tac.eu.org/cgi-bin/man-cgi?disklabel+5)

      num of spare sectors per track
      num of spare sectors per cylinder
      num of alt. cylinders per unit
      rotational speed
      hardware sector interleave
      sector 0 skew, per track
      sector 0 skew, per cylinder
      head switch time, usec
      track-to-track seek, usec

      cmon, do we need/want this information with modern storage systems, the details are taken care of in hardware, we dont need to clutter up our partition tables.

      Not something to boast about.

      lame slashdot lame filter prevented acurate formating

    2. Re:Let's not confuse FS and Partition type by Anonymous Coward · · Score: 0

      Um, yes those fields you mentioned are necessary to run soft updates. (As a linux user, you probably have not heard of soft updates. Think of a journaling file system that actually uses a dependency graph to speed things up--it's the next generation after the 1980s technology of journaling.)

    3. Re:Let's not confuse FS and Partition type by Anonymous Coward · · Score: 0

      cmon, do we need/want this information with modern storage systems, the detai
      ls are taken care of in hardware, we dont need to clutter up our partition table
      s.


      In case you didn't notice, none of this information is stored within the partition table itself. This is a machine independant abstraction, which on PC's gets stored in what ms/linux/the-bios call a partition. Since BSD is partitioning within this unit, it's called a slice rather than a partition.



      Not something to boast about.


      Why not? It means I can put 26 partitions in the space where linux/ms could only put one. This is a substantial gain considering the PC hardware limitation on disks (4 "primary" partitions, then hack-ish cruft if you want more than that).

    4. Re:Let's not confuse FS and Partition type by Anonymous Coward · · Score: 0

      if you bother to read papers, you'll find
      that journalling and soft updates are DIFFERENT approaches to solving similar problems. At this point neither one can clearly be stated as being
      better performing than the other.

    5. Re:Let's not confuse FS and Partition type by swordgeek · · Score: 2

      "The question asked for information about partitition schema, not file systems."

      Actually, the question asked about filesystems, quite clearly. The headline asked about partition types. Who comes up with the headline--the poster, or Hemos?

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
    6. Re:Let's not confuse FS and Partition type by Anonymous Coward · · Score: 0

      Actually, the poster does. But I still agree with you that this guy is a pretentious snob who read the headline and not the question.

    7. Re:Let's not confuse FS and Partition type by Anonymous Coward · · Score: 0

      Filesystems:
      If only UFS(w/ or w/o softupdates)-FreeBSD's default filesystem type didn't suck so much. Yeah, great, it's fast. Whee. Yeah, it's stable, whee. If only you didn't have to give up 8% of your drive to get it to peform at a decent level.

      UFS uses a hashing system to determine free locations on the disk. While this works well to avoid fragmentation until the disk becomes 85% full. After that point, you begin to see more hash collisions, which means the filesystem needs to find another (empty) location using another equasion. As the disk fills, more and more locations become filled. To solve this, UFS sets 8% of the disk (by default in current versions of FBSD) as unavailable to anyone but root or root owned processes. While, 8% may not sound like a lot, on a 40 gig drive 3.2 gigs are unavailable. You can adjust this with the tunefs option, but if you adjust it below 6% the algorithms used for assigning data changes to something much slower.

    8. Re:Let's not confuse FS and Partition type by aCC · · Score: 1
      Arrghhh...

      > The question asked for information about partitition schema, not file systems.

      The headline was about partition types not partition schemes. And the question was about filesystems (which makes more sense than a question about partition types anyways).

      (Does nobody even read the submissions anymore??)

    9. Re:Let's not confuse FS and Partition type by dstone · · Score: 5, Funny

      Who comes up with the headline--the poster, or Hemos?

      C) Cowboy Neal

    10. Re:Let's not confuse FS and Partition type by Sloppy · · Score: 2

      Even though the question is obviously about filesystems...

      IMHO, if you want a superior partition scheme, you should not use the linux system, which is identical in structure to the Microsoft DOS system. Instead, read about the BSD partition (and slice) system.

      The problem with BSDs partition is that most people run BSD on x86 boxes these days, so they end up putting it all inside of an old-fashioned "fdisk" style partition. Then you get the worst of both worlds. And if you go dedicated, everyone looks at you funny. "ARE YOU SURE YOU WANNA DO THAT?" Good grief, what are you supposed to say?

      If you wanna see a partitioning system that really rocks, go back to the mid-80s and you'll find something that's better than anything else in use today: Amiga's RDB. And to think that this will fade into oblivion! Gee, thanks for reminding me how badly dilapidated and decayed personal computer technology is becoming. Here I am all happy that daylight savings time has finally ended and I get my stolen hour back, and someone has to remind me of a downer.

      Using a PC these days is like touring Dunwich and Innsmouth.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    11. Re:Let's not confuse FS and Partition type by Crass+Spektakel · · Score: 1

      Linux can use nearly every known method to partition your harddrive. I use RDB, BSD-Slices, no partitioning at all, MSDOS-Partitions (the most common) and several others. I guess there are around 20 different styles of partitionizing supported today.

      BSD doesn't have fixed locations for every file. FreeBSD does have that, Net/OpenBSD has another system and darwin yet another one.
      Mayor Linux-Systems follow FHS/LSB making several Linux-System highly interoperable.

      Next time you want to bully Linux vs BSD get a clue first.

      --
      "Life is short and in most cases it ends with death." Sir Sinclair
  26. Doesn't matter. by Man+of+E · · Score: 5, Informative
    Look, if you're just running a small apache and ftp server on your pc, it probably doesn't make much of a difference. You're probably going to take heavier performance hits from all the other stuff that's running than because your file system, kernel, partition, etc is not optimal. You only need to worry about this if you're building a dedicated system that's going to take lots of hits.

    I'm running apache and ftp right now, and average traffic is about 20 hits per day. At this order of magnitude, or anywhere near it, it really doesn't matter.

    --
    Ceci n'est pas une sig
    1. Re:Doesn't matter. by agdv · · Score: 1

      I'm running apache and ftp right now, and average traffic is about 20 hits per day.

      And of course, the easiest way to change that is by telling people about it in Slashdot. Smart move. Good thing you didn't post the URL.

    2. Re:Doesn't matter. by Anonymous Coward · · Score: 0

      What about the standard 5000 Nimda/CodeRed[I..II] hits per day?

  27. ext3 by SnapperHead · · Score: 2, Insightful
    I am running ext3 on all of my machines for a few good reasons. I have ran ReiserFS in the past, but I have switched.
    • ext3 feels more responsive then ReiserFS. This isn't a real benchmark.
    • ext3 supports file attributes. Which is *VERY* important to me. I am kinda pissed off that the most important (well, one of) file attribute is s, this way, if a file is deleted, its contents are zeroed out on the platter. Good for security waykos like me :)
      chattr +a /home/*/.bash_history is a very nice feature.
    • You can mount an ext3 drive on a ext2 system. Theres no converstions that will cause data loss. Plus, it was very simple to get up and running with rh 7.2

    Of course, it has 1 big draw back, its not merged with Linus's kernel. That should be happening soon, I hope.

    --
    until (succeed) try { again(); }
  28. What's your problem with NTFS? by ergo98 · · Score: 1

    Just DON'T even think about vfat or NTFS!

    Perhaps you meant using an NTFS fs under Linux, however if not: What's your problem with NTFS? NTFS 4 and NTFS 5 are very feature laden, impressive filesystems, so I'm curious what your problem with them is, apart from perhaps that they're from Microsoft.

    1. Re:What's your problem with NTFS? by swv3752 · · Score: 1

      It is the fact that you have to run some version of WinNT to use them.

      --
      Just a Tuna in the Sea of Life
    2. Re:What's your problem with NTFS? by Anonymous Coward · · Score: 1, Informative

      I assume he means under Linux. The NTFS driver for Linux is still unstable for writing.

    3. Re:What's your problem with NTFS? by Anonymous Coward · · Score: 0

      XP uses it, and it SUCKS!!! We had a power outtage at our store, and it killed the one HP XP system. Sure I was able to make a bootable floppy on another xp system, but that was about as much as I could get. The Boot disk was a DOS mode one, which could run scandisk, but not on NTFS. there was no way to recover the system (it halted about 2 seconds into the XP screen with a disk error. We had to re-install everything. Had XP been installed on a FAT16 or FAT32 (which you can do under XP) instead of NTFS, scandisk would have run and the chances of needing a complete reinstall would have been closer to nill.

    4. Re:What's your problem with NTFS? by Anonymous Coward · · Score: 0

      Well, I hate microsoft as much as the next guy but your argument is silly. Your problem is that you could not run scan disk- not with ntfs. The fat * fs is very much a legacy fs with very few bright spots. You are talking noticeable performance hits and more if you are running fat *.

    5. Re:What's your problem with NTFS? by Hercynium · · Score: 1

      It's been my experience, that, yes, under Linux NTFS is highly unstable.

      However, it's also been my experience that under NTFS is damn unstable under WinNT as well.

      Case in point... A production system I was running several years ago crashed. (NT4 SBS, PDC) The system HD was fried but the data drive was OK (backed up on RAID anyway.) When I attempted to reinstall the OS, for some strange reason NT told me the permissions on the data drive made it unusable! I ended up having to devise a particularly dangerous registry hack (involving NT's rescue boot-disk and reinstallation procedure) just to get access to a filesystem that should have just been readable right off the bat. Needless to say the system was down for several hours.

      In another job, as a contract sysadmin for anout forty different clients, I was dealing with *constant* fs problems with NT.

      Really, I only mentioned vfat and NTFS because I've met many linux newbies who are nervous that if they don't use a windows compatible FS they will be locked into Linux forever. (not that that's such a bad thing) :^)

      While ACL's are great, you can certainly use several different patches on ext2 and ext3 for those, or even use XFS. For a small web server, though, I don't think he needs anything more than ext2.

      Just my $.02.

      --
      I'm done with sigs. Sigs are lame.
    6. Re:What's your problem with NTFS? by zmooc · · Score: 1

      The NTFS driver will probably remain unstable forever because you can't make a stable driver for a filesystem which has no documentation available (or is there?) and (especially) which changes big time with every major release.

      --
      0x or or snor perron?!
    7. Re:What's your problem with NTFS? by petard · · Score: 1

      boot from the install cd, choose the repair from console option, and chkdsk /R.

      --
      .sig: file not found
    8. Re:What's your problem with NTFS? by jerdenn · · Score: 1

      Just because you didn't know what you were doing, doesn't mean that the system sucks. You can indeed boot into DOS with NTFS drivers and run chkdsk. You may also boot into kind of a console / repair mode for NT (This came out in Win2k).
      -jerdenn

    9. Re:What's your problem with NTFS? by Anonymous Coward · · Score: 0

      Here we go, another *nix guru that knows all and has determined that an OS sucks because he doesn't know how to use it.

      Your argument is like me saying that Linux sucks because I couldn't run scandisk on my ext2 disk.

      Puhlease.

    10. Re:What's your problem with NTFS? by Anonymous Coward · · Score: 0

      Redhat's Anaconda couldn't install on my HDD as during a power-loss something went really bad on the partition table (type=0 ??). Redhat refused to install and fix the error which pissed me off to no end. So, in the end, I had to use Win98's "take no prisoners" installation which corrected the error and then install redhat over the top.

    11. Re:What's your problem with NTFS? by Anonymous Coward · · Score: 0

      1) Learn how to admin an NT system

      2) DOS bootdisk is easier, but at the cost of having MS's shitty FAT implementation silently corrupt your files over time. NTFS means no registry rot, no periodic reinstalls to resolve 'funkyness'.

    12. Re:What's your problem with NTFS? by nstenz · · Score: 1

      Wait a minute...

      The guy obviously doesn't know how to admin an NT box from the Recovery Console... That much is true.

      But what the hell does FAT/NTFS have to do with Registry rot?

    13. Re:What's your problem with NTFS? by Anonymous Coward · · Score: 0

      Did you click the security permissions and take ownership as administrator? If you have to reinstall NT, the SID of the administrator user will be different and thus it will not allow you to change the permissions on the drive. However, it will let you as administrator assume ownership of the data and then it will allow you to access the drive.

    14. Re:What's your problem with NTFS? by Anonymous Coward · · Score: 0

      sounds like you're just retarded. ntfs is the best fs there is in my opinion. maybe not under linux, but thats not what it was designed for. under any NT os its great and extremely stable.

    15. Re:What's your problem with NTFS? by blumpy · · Score: 1

      1) If you have a important server, install a UPS with autoshutdown software - regardlress of UPS or not.

      2) Take a course or learn some more about XP before using it on a important data. You can in fact do NTFS recoveries with checkdsk.

    16. Re:What's your problem with NTFS? by Hercynium · · Score: 1

      The hack *was* done from a recovery console... twit.

      The ACL keys are backed up with the registry on the recovery disks. The restoration of the user settings and ACL keys were then done from the console. Do I have to explain everything to you people?

      --
      I'm done with sigs. Sigs are lame.
    17. Re:What's your problem with NTFS? by unitron · · Score: 2
      The only hack I see mentioned was by Myrv, who said "...I could boot into Linux, copy the registry files from the fubar'd Win2K install, and write my own utility to repair it...", but before that said "I love people who say, just boot into the recovery console and fix stuff from there. Well let me tell you that that does NOT always work.", and concluded with "2) Don't trust the recovery console, it relies too much on the registry."

      You left unanswered the qusestion of what FAT/NTFS have to do with Registry rot.

      --

      I see even classic Slashdot is now pretty much unusable on dial up anymore.

    18. Re:What's your problem with NTFS? by Anonymous Coward · · Score: 0

      What is this?

      Windows magazine?

  29. Personally I prefer by A_Non_Moose · · Score: 1, Funny

    the partitions that are 6 ft. or taller with sound proofing so the music I play does not disturb my other coworkers.

    (heh, there is one in every crowd...and yes, that is me they are talking about)

    Ok, go a head and mod this down as funny.

    --
    Have you read the moderator guidelines? Well, have you, PUNK? (and I want a Karma: Gnarly option)
  30. Another redundant question. by MwtrV · · Score: 1

    Just a few days ago,

    http://slashdot.org/article.pl?sid=01/10/23/1621 22 5&mode=nested

    appeared. And the "debate" over file systems has been going on and on. The article I cited above is recent and perhaps not as relevant, but I think a lot of people who wrote replies were both sensible and informative when it came to the merits of the two most available journaling systems for Linux (as is the case with this debate. I don't see a whole lot of chilish flaming.)

    --
    mwtr / THIS SIG HAS BEEN PRAYED OVER AND MAY BE USED AS A POINT OF CONTACT (ACTS 19:12)
  31. Some Important Tips to Remember by selectspec · · Score: 4, Funny
    Ok, here are some tips regarding filesystems.

    • Make sure that whatever filesystem you choose runs with 256 colors.
    • Make sure that you pick a filesystem that has SCSI (or you could hold out for Infiniband).
    • Don't use a floppy drive in conjunction with your hard drives (it slows them down.
    • Don't be afraid to run your web server off of swap space only.
    • Mauve servers are faster than gray, but those new black cases are also pretty good.
    • Be sure that you partition your buffer cache correctly
    • Don't forget to check the syslog for any journal entries that XFS, ext3 or Rieser makes.
    • NFS and SMB are the best filesystems because they minimize your local disk space needs and they are the most reliable and efficient.
    • If you're running linux alway use NTFS
    • Put all of your files in just one directory (/) for performance increases.
    --

    Someone you trust is one of us.

    1. Re:Some Important Tips to Remember by jx100 · · Score: 1

      I'm not so sure if black is really faster than mauve. After all, mauve does have more RAM

    2. Re:Some Important Tips to Remember by Anonymous Coward · · Score: 0

      WHERE IS THAT LINE FROM? I must know now!!

  32. Partition? by Density_Altitude · · Score: 1

    If we take the "partition" word by it's definition, a hard drive partition would be a way to separate the hard drive into one or more distinct parts. Now, those parts aren't called "partitions"; they are part of the hard drive partition scheme if you like. But we often refer to those parts as partitions which is wrong: a hard drive can be partitionned in only one way at any given time.

    My question is how then should we call those "parts" ?

    Now to answer the filesystem question I would suggest using ReiserFS. I used it for a couple of months with good results and without any problem. It works well also on software raid1...

    --
    delete free(system.gc);
    1. Re:Partition? by swordgeek · · Score: 1

      Partition is a verb. AND partition is a noun. It's not a difficult concept. Nor is it new.

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
  33. web server by obi327 · · Score: 1

    i run a few basic web/ftp servers that get about 1000 hits a day. they run slackware 8.0 with ext2 filesystems. however, if you are expecting a short number of hits, it really doesnt matter what filesystem you use, more it depends on what distribution and what software you are using.

    --
    The dog got loose on my computer, and now there's XP all over the screen. -Paul www.ploeb.net
    1. Re:web server by Anonymous Coward · · Score: 0

      I was wondering if there is some way to figure out how large of a pipe is needed for 1000 page views/5000 page views/slashdot? Is there some formula, for example a 50k static page, max number of simultaneous users, etc.? What can I expect with a 128K upstream DSL connection? 256K?, etc. I saved the post about slashdot's experience on 9/11. How large of a pipe is needed for that? 2 t-1's? A t-3? Just curious about slashdot's pipe, but the smaller pipe question may help me decide between a hosting company for several of my web sites, with cable modem for my ISP access, and DSL, and rolling/hosting my own. Thanks.

    2. Re:web server by Anonymous Coward · · Score: 0
      a short number of hits
      hmm... i didn't know numbers had height...
      i don't think the first two sentences were very relevant,either.
  34. it doesn't matter by metalhed77 · · Score: 1, Redundant

    if it's a small server (i'm assuming under 5000 page views a day) It won't matter what you go with unless your running off a 486. I'd say just go with one that journals for crash recovery, but if it's a small server you won't notice much of a speed difference

    --
    Photos.
  35. My fstab by LiENUS · · Score: 1

    My fstab looks something like this (nonrelevant parts snipped)
    /dev/hda3 / ext3
    /dev/hda2 swap swap
    /dev/hdb1 /glftpd/site ext3
    /dev/hda1/ / tmp reiserfs

    1. Re:My fstab by Anonymous Coward · · Score: 0

      Why do you prefer to have the core data on ext3, and yet, to Reiserize your temp?

      Wouldn't administration be easier if you've standardized all on ext3?

    2. Re:My fstab by LiENUS · · Score: 1

      I dont need the special features of ext3 for tmp and my tmp dir usually has lots of small files in it (lots! i have a cron that doesnt delete its tmp files)

    3. Re:My fstab by AndroSyn · · Score: 1

      Why not just use tmpfs for /tmp. This is what Solaris does, and is supported in 2.4.x. Basically tmpfs uses your swap partition for the /tmp filesystem. So, upon reboot /tmp is cleaned and you never have to worry aabout it.

  36. The Default by gabeman-o · · Score: 1

    There is probably a reason for the distribution you are installing having a certain filesystem as default :)

  37. ReiserFS by Anonymous Coward · · Score: 0

    > It still corrupts data.
    Yes and No. I've been using it for ages. Never had a problem until Mandrake 8.0. What a disaster. I'm back using it again with 8.1 (am thinking about going back to rh, though) and still like the speed. No problem so far. but my total confidence in it is somewhat shaken. Since 1995, I had no problems with linux until 8.0, where I have lost 2 IBM drives, and seperatly, a corrupted partition.

  38. My system would crash often by luugi · · Score: 1

    I work on graphic drivers for Linux, which unfortunatly leads to a lot of system freezes. But i recently changed to ext3 and it has been a major time saver.

    --
    Think like a man of action, act like a man of thought.
  39. Which Partition Types are Superior by jkirby · · Score: 1

    Partitons and file systems are different. It does not matter waht the partition type is; it is still an array of 512 byte sectors.

    I personly like JFFS. Open source available from IBM. I also like JFFS in conjunction with LVM. LVM is awesome. Its snapshot feature is very useful in backing up active systems.

    --
    Jamey Kirby
    1. Re:Which Partition Types are Superior by Anonymous Coward · · Score: 0

      JFFS ???
      dont you mean JFS, JFFS would be the Journaling Flash-FileSystem and i doubt that it has been ever used in conjundtion with LVM till today, i run it on my iPaq though ;)

  40. GAH! No sense of humor whatsoever!!! by Anonymous Coward · · Score: 0

    heh.

    When CmdrTaco said humor was subjective, it does not mean you subject posters to your lack of humor and mod them down.

    Sometimes humor means straying offtopic, oh, the horror of it all. (hint: dripping with sarcasm...seeing as humor escapes most ppl, sarcasm is damn near stealth mode).

    (sigh)

    "there is a limit on my sig, and I don't char, there is a limit on my sig and I don't char...."

    Time to switch to plan b. Make a new account because I seem to be mistaken for an AC, My nic on /. is also a reflection on my sense of humor.

    Yeah, I'm tenacious, yeah, I'm off topic, yeah, my humor is esoteric, yeah I'm posting anon.

    Wandering back on topic, some moderators are not using a JFS...so (watch out here comes the funny part if you are not humor impaired) GO FSCK YOURSELF.

    Heh, a little venting, I feel better now.

    Laughter is the best medicine, slashdot moderators are the disease.

    Like the line from Aliens "Did I.Q's just drop suddenly?!". Slowly I start to realise this is a retorical question on slashdot.

    I give up, you win.

  41. Related question: Ext3 with ReiserFS? by FleaPlus · · Score: 1

    I currently have an ext2 / partition, with ReiserFS as my /home partition. I'm considering upgrading to the newest -ac kernel, compiling in ext3 support, and converting my ext2 partition to ext3.

    Does anybody know of any problems with running both journaling filesystem types at the same time?

    1. Re:Related question: Ext3 with ReiserFS? by Anonymous Coward · · Score: 0

      Um, I would think it might huge up a bit more of your CPU. but it should not be noticable.

  42. "dangerously dedicated" is that by mr · · Score: 2

    Notice how that is no longer an option in the later 4.X series?

    It 'was' dangerous....if you did any kind of CVSup and rebuilt your kernel, things like top would stop working. SCSI drives formatted on DPT RAID cards would boot with an error on Adaptec cards, and a upgrade from 3.x to 4.x would break.

    If you ran in a non-dedicated mode, rebuilds had no effect. Same with the SCSI issue.

    --
    If it was said on slashdot, it MUST be true!
  43. Another facet to this discussion... by Hercynium · · Score: 1

    I noticed another poster mentioned partitioning schemes vs. file systems... It certainly is a good point to bring up and one that is relevant to the file system used.

    I personally think the default partitioning schemes used by most Linux distros suck. BSD clearly has an advantage because of the strict standard. It's also better because it's more strict and (IM*NTBC*HO) logical in the standards for the placement of files.

    Depending on the size of your HD, the space required by the hosted data, the required reliability/resilience/uptime, the partitioning and filesystem schems could vary drastically. For a newbie, it's best to begin with the default anyway, but I'd reccommend looking into alternatives anyhow.

    BTW, no offense intended, but I'm assuming the poster is a newbie simply by the nature of the question asked. I was once a newbie too... ahhhh, the good old days of innocence and discovery, and getting flamed by the wannabe gurus with ego problems... :^)

    --
    I'm done with sigs. Sigs are lame.
  44. My favourite filesystem by Zulu+One · · Score: 0

    I like FAT because reiserfs and ext are for wusses who actually want to read data from the partition after they've written it. This is why, although my linux root partition is ext2 (yes, still), all of my important files are on a FAT32 partition.
    OK, to be honest it's because Stupidity 98 doesn't read ext partitions. I would like to use something better. In fact, I want a filesystem that recovers better from crashes than ext2, so I might consider changing at some point. Still, I like FAT16 for sheer nostalgia value. And NTFS still gets me sometimes. Just... go gently with it.

    --
    http://www.doublezero.uklinux.net/
    Doublezero: like Slashdot, only less useful.
  45. A crypto filesystem? by magi · · Score: 4, Interesting

    Is there any stable crypto filesystem for Linux?

    I found a "CFS", but the version was just for kernel 2.2.x. I didn't find a 2.4 port.

    SuSE 7.3 ads say it has a "CryptoFS". Does it work well? Where can I get it, if I don't want to install SuSE?

    An easy-to-use crypto fs would be enormously important especially for laptops in corporate world. I think W2k or XP have some kind of encryption options, and if Linux can't provide a good alternative, it may be a problem in more paranoid companies.

    Of normal filesystems, I've found ReiserFS stable on my two machines during my 6 months of use. I converted from ext2 after it corrupted mysteriously. Unfortunately, RH still doesn't support ReiserFS, even optionally, which I think is really silly. SuSE and Mandrake do.

    1. Re:A crypto filesystem? by AaronW · · Score: 2

      I have been using the SuSE 7.2 crypto file system for some time without any problems. It's no speed demon, but it should be secure. When installed you are prompted for the password while booting up. It should be easy to change so you can enter the password only when you want to.

      --
      This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
    2. Re:A crypto filesystem? by Anonymous Coward · · Score: 0
      > Is there any stable crypto filesystem for Linux?

      > I found a "CFS", but the version was just for kernel 2.2.x. I didn't find a 2.4 port.

      Maybe that's because we still have to wait for a stable (and non-braindead, think vm) Linux 2.4?



      However, most of this `crypto-filesystems' aren't filesystems the way ext[23], ReiserFS, XFS, JFS etc are [Hey - this thread still lacks a `we don't need journaling, softupdates are better - use FFS pn BSD!' post]. They are merely a method to encrypt a `real' filesystem, via loopback devices, just the chosen name is misleading.



      BTW, the point that SuSE includes ReiserFS and RedHat doesn't isn't that surprising - SuSE invested heavily in ReiserFS development. And, in my experience, ReiserFS does indeed work in a SuSE way (like e.g. SuSEconfig does...) - it does it's job well, as long as you don't consider `store my data in a reliable way' as it's job...

    3. Re:A crypto filesystem? by marsaro · · Score: 1

      Why not install SuSE? I use Crypto on all my systems for my /home It is great, and SuSE is better than RH for this and a 1/2 dozen other technical reasons. ONe, which his thread is based on is the Reiser FS support. The only Journaling FS in the Kernel to date.

    4. Re:A crypto filesystem? by fialar · · Score: 1
      Try LOOP-AES and stay far, far, FAR away from the international kernel patch if you are using 2.4 kernels. It has bad bugs in it which will crash your crypto'd FS.

      (moderators please mod this up to get the word out.. thanks!)

      -fialar

    5. Re:A crypto filesystem? by Admiral+Burrito · · Score: 2

      I found a "CFS", but the version was just for kernel 2.2.x. I didn't find a 2.4 port.

      If it's the CFS originally by Matt Blaze, then it should work fine without any kernel support other than NFS client. CFS just runs as a user-mode NFS server. If you can mount an NFS filesystem, you can mount a CFS file system. CFS even works on non-linux systems, such as FreeBSD.

    6. Re:A crypto filesystem? by srw · · Score: 1

      > and stay far, far, FAR away

      Yes, but how will I know when I'm far enough?

  46. WHO CARES? FUCK THE INTERNET by Anonymous Coward · · Score: 0


    GO OUTSIDE. Get a life. Stop wasting your time with useless bullshit that can so easily be taken away from you. Maybe put your money into some useful cause.

  47. VFAT, of course! by Kymermosst · · Score: 0, Flamebait

    How can 70%+ of the world be wrong?

    Look at all the features... long file names, abbreviated file names, many allocation sizes, and backwards compatibility all the way to 1981 if you want!

    What, it doesn't support any kind of access control, you say? You don't need it anyway. After all, it's always nice when anyone at your computer can remove any file they want, like some random libraries from the system folder.

    With the backing of an "innovative" industry giant like Microsoft, VFAT is surely the filesystem choice of the future!

    (this is supposed to be funny)
    --
    "Alcohol, Tobacco, Firearms, and Explosives" should be a convenience store, not a government agency.
    1. Re:VFAT, of course! by Anonymous Coward · · Score: 0

      Bah, you people have no sense of humor... obviously this was intended to be funny, not flamebait

  48. Linux == insecure, by default! by Anonymous Coward · · Score: 0

    Ummm, why Linux? If you go Linux, make sure you have this weeks latest and greatest kernel or else, someone will r00t your boxen (hopefully you know about all those security holes in that last few years, that Alan/Linus never told anyone about) so update with tomorrow's kernel, and the day after, and, the day after... etc.. etc.. or else behold in the insecurities of Linux, or simply go OpenBSD if you want REAL security!

    1. Re:Linux == insecure, by default! by Anonymous Coward · · Score: 0
      > If you go Linux, make sure you have this weeks latest and greatest kernel or else, someone will r00t your boxen

      That's Bullshit! Especially the latest Linux kernels were crap! ;-)



      > or simply go OpenBSD if you want REAL security!

      The point is, nobody talked about security. The Default Linux User[TM] doesn't care - as long as it's not Windows, he's confident. And if you need more, there's always the latest secure kernel patch from www.britneyspearsnude.com/trustmecauseitellya, which does all I need...

  49. Upgrade to Dynamic Disk? by reezle · · Score: 1

    Anybody else here ever completely kill a Windows 2000 system by upgrading a disk from basic to dynamic?

    I had two different systems completely crap out on me during the interval between 'You must reboot your POS Windows Box for Changes To Take Effect', and the inevitable "No Boot Partition Found - System Halted"

    One system I recovered, the other was a complete loss. Emergency Disks, Repair Installs, Parallel Installs, etc all claimed the disks were simply 'damaged'. Disk sector editors were about the only useful tools when I was done.

    All this, so that the OS would allow me to mirror a few volumes... :)

    1. Re:Upgrade to Dynamic Disk? by man_ls · · Score: 2

      Windows 2000 can't boot off a dynamic drive, because the OS itself only establishes the dynamic volume after it is loaded. Before that time, even to the BIOS, they are seperate drives.

      Dynamic Volumes == Software RAID. The data is stored on there, but the partition tables and FAT are so mangled that converting back and forth, or even just removing one of the drives and swapping in another, will render all data across all volumes unreadable.

      MSKB has an article about this, I don't remember the number.

      JKoebel

  50. You first. by Anonymous Coward · · Score: 0

    n/t

  51. oh why oh why do i laugh at such stupid things by Anonymous Coward · · Score: 0

    this troll cracks me up every time i've seen it. and i must have read it about a million times.

    1. Re:oh why oh why do i laugh at such stupid things by Anonymous Coward · · Score: 0

      Yeah, looks like the "Stephen King, 52, found dead" troll got himself a new story.

  52. Here, Pick This One by Lethyos · · Score: 1, Offtopic

    Consider the range 0x00-0xFF (inclusive). Randomly pick a number in that range. Set that to your file system and get amazing results.

    Really, this is getting pathetic. We've a few too many pointless and irrelevant (come on, a story based entirely off a screenshot?!), or hopelessly outdated subject matter into the on /. the past couple days.

    Yes I am being a troll and I apologize, but I want to know why intelligent stories (maybe a couple that I've sent in) get rejected, and this nonsense gets posted in the main column. Get real! EVERY Linux distro I have EVER used starting with Slackware 3.0 has always recommended using ext2 as the Linux Default. (You'll notice certain partitioning utilities make this clear.) How can anyone disagree that this is a newbie Linux question? Posted on /.'s front page! Easily answered if someone would simply visit a documentation resource and RTFM.

    The Ask Slashdot forum has traditionally seen questions that are difficult to answer and need expert advice. They usually lend some insight into a problem or ask questions many of may not have considered.

    This guy just asked a question regarding Linux installation. What the hell? Next thing we'll see is an Ask Slashdot question with the following:

    "Hi, I wanted to ask the /. community. I'm installing WindowsXP on my server where I'm serving Samba and web pages for my friends. The installation program asked me if I want to use FAT or NTFS. WHICH ONE DO I USE!? I'm so confused about what partition type to use! I hope the /. community can lend some insight!"

    Go ahead and mod me down. I don't care, but I think there aughta be another voice expressing irritation at the reduced quality for a service that may become subscription in the near future (or drown us in ads). I don't think that's major news or anything someone in #linuxhelp on the Undernet couldn't have answered with a flood of flames.

    --
    Why bother.
  53. Troll this. by Anonymous Coward · · Score: 0

    #1 Uh, yea it does.
    #2 So what?
    #3 Do you really?
    #4 This is bad??? How?

    1. Re:Troll this. by LiENUS · · Score: 1

      #1 no it doesnt it corrupts your fs if you write to it
      #2 his arguement was that linux didnt support acls
      #3 uhh thats not a response
      #4 his arguement was thar journalling was bad and ntfs wasnt journaled.

    2. Re:Troll this. by ninewands · · Score: 1

      #2 So what?

      While the Linux port is fairly recent, XFS (which supports ACLs in ways NTFS can only dream about) has been in use on production servers for almost 16 years. This would sort of indicate that the serious bugs are already out and any performance hits are a result of inappropriate use (XFS is optimizedfor HUGE database files) and/or incomplete optimization of the Linux port of XFS.

  54. yet another ask slash RETARD by Anonymous Coward · · Score: 0

    here's yet anther pitiful ask slashdot. these things are really lame aren't they. digitalmonkey2k1 is a fucking moron... prime example of slashsnot

  55. huh? by Anonymous Coward · · Score: 0

    It would really help if you actually read his question before answering.

  56. Don't tell me what to fucking do by Anonymous Coward · · Score: 0

    I'll just reply to you, then I won't be replying to the original poster. Are we happy?

    1. Re:Don't tell me what to fucking do by The+Kenneth · · Score: 0

      yeah thats fine.

  57. XFS - Is good. by Anonymous Coward · · Score: 0

    Have XFS on a few production boxes (well, getting ready for rollout !). Once I proved I could boot/recover from CD and do live backups / snapshots, the picture was complete. It has been debugged logically already.

    If the code would find its way into the main kernel source, it would make the choice easier. The Bootable CD iso image is available on ftp://oss.sgi.com/projects/xfs/download/Release-1. 0.1/installer/ Makes a nice complement to RHL 7.1. A few other distros also have support for XFS.

  58. RedHat 7.2 *does* include ReiserFS... by Kelson · · Score: 1

    ...just not as their default filesystem.

  59. Speed improvements in ext3 by David+Jao · · Score: 2
    Unless they've made some serious improvements in the past few months, the filesystem still writes at 50% the speed of ext2

    They have made improvements, and in my experience ext3 is faster than ext2. See for example the Michael Johnson email:

    Despite writing some data more than once, ext3 is often faster (higher throughput) than ext2 because ext3's journaling optimizes hard drive head motion.
  60. Type 83 of course! by Leto2 · · Score: 1

    The answer to today's question is Type 83 of course.

    Oh wait, are we talking about partition types or filesystems here?

    --
    <grub> Reading /. at -1 is like driving through Cracktown in a convertible that is stuck in 1st
  61. you don't get something for nothing by mj6798 · · Score: 3, Informative
    Journaling file systems have extra runtime overhead. If your system is disk bound, you lose more time on journaling while the system is up than you would over the rare fsck. Your recommendation is particularly incongruent because you recommend, at the same time, web servers that give better performance only in very highly loaded systems (unlikely to be encountered in practice).

    Other problems with journaling file systems are that they are more complex, less mature, and have appeared only more recently in the Linux kernel, meaning there is a higher probability that they have some problem.

    If you can't tolerate the few minutes of downtime resulting from an fsck, then a journaling file system is not going to help you either since machines become unavailable for lots of other reasons. In that case, you need network mirroring with a hot failover. Journaling file systems are more about convenience than any particularly rational engineering tradeoff.

    Altogether, my recommendation is: don't pick software just because it's hot and new. For most users, ext2 with Apache makes a great web server platform. Apache is fast enough for any kind of Internet connection you are likely to have (Microsoft could probably serve all their static content from a single Apache server). If you like the convenience of a journaling file system and don't mind the performance hit, maybe you want to consider ReiserFS, which offers a lot of other useful features.

    1. Re:you don't get something for nothing by Anonymous Coward · · Score: 0

      "If you can't tolerate the few minutes of downtime resulting from an fsck, ..."

      The few minutes of downtime? Just how small are your filesystems, anyway? For Large filesystems, it takes 30-90 minutes, not a "few".

    2. Re:you don't get something for nothing by topham · · Score: 2
      While I won't get into the reliability of Linux journalling filesystems I can tell you that few companies would use a high-end system without such a filesystem.

      You can waste a very large amount of time checking a filesystem after the system goes down unexpectedly (for whatever reason).

      A journaling filesystem adds very little overhead, except when a large number of files are created, or deleted. As such, it is NOT going to have a large impact to a well configured webserver

    3. Re:you don't get something for nothing by mr3038 · · Score: 2
      For most users, ext2 with Apache makes a great web server platform.

      I wouldn't use ext2 for any server even if I didn't need journaling. ReiserFS should be faster during reading especially if you happen to have many small files or a couple huge files. Journaling shouldn't matter performance if you aren't updating anything. And if you're, you should be using journaling anyway. So in the end, if you choose ReiserFS over ext2 you should get at least better performance. You might also get journaling as an added bonus.

      I don't know if ReiserFS is the best journaling filesystem, but it's the one I have used and it has never disappointed me. OTOH, I have lost ext2 partition once... The only reason to use ext2 is either you're really low on memory (kernel size) or you have to use ext2 for backwards compatibility - for example I know about driver to read ext2 partitions from windows but I haven't found a one for reiserfs. Another way is obviously a piece of cake.

      --
      _________________________
      Spelling and grammar mistakes left as an exercise for the reader.
    4. Re:you don't get something for nothing by Kuad · · Score: 1

      While I won't get into the reliability of Linux journalling filesystems I can tell you that few companies would use a high-end system without such a filesystem.

      Doesn't seem to hurt Sun's sales any. And before you mention that any large Sun customer would use the Veritas suite, I'll point out that VxFS is not a proper journaled filesystem.

    5. Re:you don't get something for nothing by roybadami · · Score: 1
      Journaling file systems have extra runtime overhead. If your system is disk bound, you lose more time on journaling while the system is up than you would over the rare fsck

      On most Unix systems metadata journaling is likely to improve performance, because it eliminates synchronous metadata writes.

      Linux is a bit of an exception, because ext2 doesn't do synchronous metadata writes anyway...

    6. Re:you don't get something for nothing by topham · · Score: 2
      define 'proper jounraling filesystem', and then show a list of Linux filesystems that exceed VxFS capabilities.

  62. NTFS Revisions by Anonymous Coward · · Score: 0

    WinNT 3.51 = NTFS 1.0/1.1
    WinNT 4.0* = NTFS 1.1
    WinNT 5.0** = NTFS 5.0
    WinNT 5.1*** = NTFS 5.1

    *WinNT 4.0 Can use read/write NTFS 5.0 w/SP4. But not all partition functions are available. AKA Forced Upgrade's required to NT5

    ** WinNT 5.0 = Windows 2000
    *** WInNT 5.1 = Windows XP(not includeing flavors)

    1. Re:NTFS Revisions by ergo98 · · Score: 1

      Just as a point of reference, in the Windows world it is usually referred to as "NTFS 4.0", and this designation was the reason why MS officially named the version in "NT 5" "NTFS 5.0". Even historically lots of references have backtracked and renamed it NTFS 4.0 due to the fact that logically it goes with NT 4.0.

      Just thought I'd mention that as the only group that I've seen that consistently still calls it 1.0 or 1.1 is the Linux crowd. For the rest of us it's correlated with the NT version that it was introduced with.

      Cheers!

  63. Some additional questions by Phantasmagoria · · Score: 1

    I'm setting up a web-server and file-server for my dorm - which shall have upto 100 computers accessing it. The files are mostly small ones - almost all less than 10 MB. I want a journalling filesystem that journals file data as well as metadata. What should I use?

    --
    Loban Amaan Rahman ==> Anagram of ==> Aha! An Abnormal Man!
    1. Re:Some additional questions by LiENUS · · Score: 1

      ext3 i believe does this

  64. While on the subject of partitioning... by crashnbur · · Score: 1
    What is the best way in Windows ME to reduce file cluster size from 32KB to 4KB? Every installation of Windows ME I have used (except this one) uses 4KB clusters, but my newest system uses 32KB clusters, which makes for a lot of wasted space on the hard drive.

    I have Partition Magic 7, but I have not installed it. Is that my best bet? Or is there an easier method?

    1. Re:While on the subject of partitioning... by thehamster · · Score: 1

      What is the best way in Windows ME to reduce file cluster size from 32KB to 4KB? Every installation of Windows ME I have used (except this one) uses 4KB clusters, but my newest system uses 32KB clusters, which makes for a lot of wasted space on the hard drive.

      I have Partition Magic 7, but I have not installed it. Is that my best bet? Or is there an easier method?

      Sounds like your latest installation is using old FAT (FAT 16 / VFAT) rarther than FAT32. Install Partition Magic and use it to turn it into a FAT32 partition. Cant remember quite how, but its pretty simple, although it might take some time.

      Or I could be spewing garbage out of my ass, which is highly probable.

      Although a lot of people here would probably say a better bet would be to indtall Linux / FreeBSD / BeOS / RISC OS / get a slide rule.

      --
      -- This is not a sig. But I'm a liar.
    2. Re:While on the subject of partitioning... by Oswald · · Score: 1

      Well, figure the odds that this hasn't changed in three years, but in Win98, the easiest way to make the change is Start->Programs->Accessories->System Tools->Drive Converter. I only implemented the change about 3 months ago (maybe because it was buried so deep in the menus), and it went off without a hitch.

  65. ext2 mount readonly by Anonymous Coward · · Score: 0

    make it simple and fast: use ext2 and mount it readonly. no journaling, no overhead. if this is not possible, you can use any of the supported fs.

  66. KISS by Anonymous Coward · · Score: 0

    If you don't know enough about the issues to make an informed decision, you should use ext2. If you think asking about it on Slash-the-banner-ads-dot will help, then you REALLY should just use ext2.

  67. Rescue Floppy Support for ReiserFS? by Vagary · · Score: 1

    Which rescue floppies support ReiserFS? This is the primary reason I am avoiding JFSs at this time:

    • ext3fs can't be fscked
    • All other JFSs can't be accessed at all

    My desktop has lots of beta software and no UPS, therefore Tom's RootBoot is not an unheardof occurance.

    1. Re:Rescue Floppy Support for ReiserFS? by AndroSyn · · Score: 1

      What crack are you smoking. ext3fs can be fscked just fine by a recent version of e2fsck. As for other filesystems, build your own damn boot disk.

    2. Re:Rescue Floppy Support for ReiserFS? by cloudmaster · · Score: 2

      All of them, once you build a kernel with support and add in the tools you need.

      VMWare is pretty cheap and plex86 is free (as is Bochs) if you need to run stability-compromising software as root (create a second account otherwise). Now you can have stability *and* a modern filesystem. :)

  68. Depends by Anonymous Coward · · Score: 0

    If you are thinking of a small site without much requirements about reliability about the stored data Linux with some of the budget journalizing filesystems.

    If you have high requirements about the correctness of the data and data-corruption you should get Solaris+Veritas.

  69. Recovery Console does NOT always work. by Myrv · · Score: 1


    I love people who say, just boot into the recovery console and fix stuff from there. Well let me tell you that that does NOT always work.

    While trying to watch a DVD on my Win2K system one day it just crashed. Upon reboot I get a blue screen. Not a problem I think, I'll just use 2Ks much vaunted recovery console, but wouldn't you know it, every single safe mode also blue screened. Using bootdisks and the install CD didn't do any better. My system was completely locked out. If it wasn't for the fact that my system files were all installed on a FAT partition I would have had to reinstall from scratch. As it was, I could boot into Linux, copy the registry files from the fubar'd Win2K install, and write my own utility to repair it (the install disc registry repair feature and the repair disk both failed to fix it).

    This taught me several valuable lessons.

    1) Always install your system files on a FS that can be read from a DOS bootdisk or similar
    2) Don't trust the recovery console, it relies too much on the registry
    3) The install disc sucks at doing any kind of repairs
    4) Repair Disks are not much better
    5) Never again try to use the TV out feature on my GeForce2 MX

    1. Re:Recovery Console does NOT always work. by Anonymous Coward · · Score: 0

      I quoth:

      "1) Always install your system files on a FS that can be read from a DOS bootdisk or similar"

      You can have DOS read ability to NTFS, that's been doable for a while now. Go to www.sysinternals.com.

      "2) Don't trust the recovery console, it relies too much on the registry."

      That's why you back up the Registry weekly. Backups, man, backups!

      "3) The install disc sucks at doing any kind of repairs."

      Of course, that's not its intended function. You wouldn't expect a bus to get gas milage comperable to a Geo, would you?

      "4) Repair Disks are not much better"

      It's better to have a boot floppy that accesses a CD for your utilities. You're limited by the size of the floppy for what you can accomplish.

      "5) Never again try to use the TV out feature on my GeForce2 MX."

      If that truly caused the failure, then there's something wrong with the driver, not the underlying operating system. Did you have the newest drivers?

    2. Re:Recovery Console does NOT always work. by Myrv · · Score: 1


      You can have DOS read ability to NTFS, that's been doable for a while now. Go to www.sysinternals.com.


      Yes, I could pay $250 for a NTFS driver for DOS (having read only support is useless when trying to repair a disk) or I could just keep the system files on a FAT filesystem accessible by my 5 year old DOS disks (or better yet my Linux boot disk). Micrsoft should really provide a bootable disk solution with R/W capability with the OS.

      That's why you back up the Registry weekly. Backups, man, backups!

      That's essentially what I did. Using an old backup as a template I merged recent changes into it while avoiding the damaged areas.

      Unfortunately my home system is not a mission critical setup so I usually only get around to backups of the registry once a month. Any system that relies so heavily on a 20+ meg file that is so fragile it requires nightly backups, is poorly designed in my opinion. MS should really treat the registry in a journalled like fashion where you can roll back changes or damage. I was originally under the impression that Win2K did do this to a limited extend (i.e. it kept a 'last working' copy of the registry) but my recent experiences showed me otherwise.

      Of course, that's not its intended function. You wouldn't expect a bus to get gas milage comperable to a Geo, would you?

      If the install disk isn't intended to perform repairs why does it have the Repair option? At the very least it should be able to perform a registry validation. It should also be able to merge in a default base registry without blowing away all the application specific keys.

      It's better to have a boot floppy that accesses a CD for your utilities. You're limited by the size of the floppy for what you can accomplish.

      I have no problem with this. In fact I typically carry the business card sized Linux Rescue CD around with me. The problem is still in accessing the system files once you've booted with a floppy.

      If that truly caused the failure, then there's something wrong with the driver, not the underlying operating system. Did you have the newest drivers?

      Yes I did have the latest drivers. I downloaded them because the previous version of the drivers didn't work either. That said, I'm sure it wasn't the drivers that corrupted my registry, but the hard reboot I had to perform after the drivers locked my computer up solid. It's still a cause and effect problem though. The drivers lock my computer up when I try to use the TV out feature. The subsequent hard boot of my computer puts my registry at risk. Ergo I don't use the TV out feature anymore.

      Now, yes, I will grant you that perhaps if my system drive was NTFS my registry may not have been at risk by doing a hard boot but I don't know for sure. Anyway, there are many other ways to corrupt the registry without hard booting.

      My concern though is that Windows should protect the registry against this kind of damage regardless of filesystem.

      Andrew

  70. My message of peace by blair1q · · Score: 3, Funny


    Can't we all just thrash along?

    --Blair

  71. Re:tar by GaCRuX · · Score: 0

    And here's me think that tar (Tape ARchive ??) was *made* for backing up (onto tapes)... no?

  72. Ask Slashdot: How do I get on the main page? by djroute66 · · Score: 1

    djroute66 writes "How do I get slashdot.org's main page while trying to look as intelligent and suave as possible?"

  73. word by Anonymous Coward · · Score: 0

    Spoken rationally.

  74. reiserfs by Anonymous Coward · · Score: 0

    is not the default fs for suse.

  75. ReiserFS... by Malor · · Score: 3, Informative

    Per Red Hat's RHCE training, ReiserFS is explicitly designed for the case of extremely fast access to many small files. It also uses space more efficiently with small files than any other filesystem on Linux, because it is able to glue together the small tails of the files into shared sectors.

    Example: You write a 513-byte file to a filesystem with 512-byte sectors. On other FS types, that file will take 2 sectors. On Reiser, it will take 1 sector plus change. Numerous small files of this type can have their tails packed into the same shared sector. I do not know the overhead in bytes per file, and thus don't know how many tails you can put into a given sector.

    It also handles a very large number of files in the same directory well. Most other FS types have problems if you dump 10,000 files into a directory. It is my understanding that Reiser deals with this extremely well.

    However, there is one drawback. If you are using LILO, the tail packing can cause you much grief. Lilo does not understand tails. It will be unable to execute its own second part or the kernel itself if either has had a tail-pack done. Thus, you should likely use a separate /boot partition, and make that partition ext2 or ext3. Alternately, you can add the 'notails' option to your /etc/fstab file to turn off tail packing. If you aren't using many small files, this will not be a huge loss.

    Mandrake 8.0 came with a 2.2 kernel with ReiserFS backported. DO NOT try to use ReiserFS with any software RAID in any Linux 2.2 kernel. Make sure you update to 2.4. I believe 8.1 comes with 2.4 standard, so it shouldn't be an issue anymore with that distribution.

    There have also been numerous bugfixes in the Reiser code over the 2.4 releases, so you will probably want to go with as recent a kernel as you can. Linus' 2.4 kernel tree has the reputation of being unstable, so you may want to use Alan Cox's branch until the official tree stabilizes better.

  76. Only one thing to say by PurpleFloyd · · Score: 1

    Damn, what an incredible troll. At first glance, it looked like a legitamate post, but after reading it more deeply, its true nature became obvious. Sir or madam, I salute you!

    --

    That's it. I'm no longer part of Team Sanity.
  77. Time to burn some Karma, oops - AC's have no karma by Anonymous Coward · · Score: 0

    How about /. gets a licence for the Ask Jeeves engine so we don't have to read crap like this?

    Partition types?! Honestly, this kind of stuff should be in a HOW-TO... Where is it going to go from here? This is going to end up turning into an Internet version of a write-in newspaper colum (Dear Slashdot, anyone?). We're going to have people asking things like:

    "Dear Slashdot, I can't sign on to AOL anymore, what's wrong?"

    "Dear Slashdot, my cat pissed in my monitor and now it smells bad and won't work, how can I fix it?"

    "Dear Slashdot, what is the web address for jackinworld.com, I want to learn how to masturbate."

    Ugh.

  78. Yup by mortonda · · Score: 1

    Agreed - it even got modded up! That was a well done troll.

  79. Options are just as important by Tony+Hammitt · · Score: 2

    I'd recommend that you put your data in a ReiserFS logical volume which is part of a volume group spanning two disks, mirrored. And turn off updating the access times for files with '-o noatime' and use SCSI.

    Going mirrored will give the OS the opportunity to get the data from either spindle on reads.

    just my $0.02

    1. Re:Options are just as important by ers81239 · · Score: 1

      I would recommend getting 2GB of RAM and just running the whole thing in memory. That way your reads are measured in ns instead of ms.

      just my $2,312,312,123,121.02 of advice.

      PS-Also consider offsite storage of backups for disaster recovery.

      --
      there are 2 kinds of people. those who divide people into 2 kinds, and those who don't.
  80. If you are talking about performance... by SCHecklerX · · Score: 2

    I don't know which FS is superior, but you might want to sersiously consider using a RAID.

  81. partition types? by daft_one · · Score: 1

    What are these, different filing systems y'all have for your punchcards? Here in Montana, we just sort 'em by date. And, umm, we keep good daily journals.

  82. You're wrong. You didn't read what I said. by Gendou · · Score: 3, Informative

    Although advanced journaling filesystems only journal metadata, some journaling filesystems journal everything: when a disk write happens, the entire write is written to the journal file, then it's written to the real file, then it's deleted from the journal file.

    When Ext3 was first created, it COULD NOT journal metadata -- the only option was full file journaling, which was incredibly slow. Don't tell me I'm wrong, because I read the original release notes which said that metadata journaling was not available yet. I believe that Ext3 can now do metadata-only journaling -- somebody correct me if I'm wrong -- but it's a fairly recent development, within the past year or so.

    This mail message from about a year ago says that metadata support was "in an early state" at the time. I don't know if it's been perfected since then or not. But the e-mail proves that at one time, Ext3 could NOT do metadata-only journaling, which flat-out disproves your post that all journaling filesystems only journal metadata.

    And RAID quite frankly has nothing to do with it; I can't even imagine why you brought it up because it's absolutely irrelevant.

  83. Re:Let me get this straight... by Anonymous Coward · · Score: 0

    Totally agree. And you know who is behind the WTC disaster and the Anthrax scare... Linus Torvalds.

  84. Why? by jotaeleemeese · · Score: 1

    For a little home PC serving 2 pages per day?

    --
    IANAL but write like a drunk one.
  85. reiserfs, xfs and caching by anden · · Score: 2, Interesting

    After using reiserfs for a year++ and now having switched to xfs, my recommendation is the latter. There is a simple reason to this: reiserfs caches a lot. Even with 512Mb RAM I always ended up with swap after doing a few file transfers, and for a ftp site that is not so good, at least not if you plan to do other things with the computer as well.
    A simple solution is of course to disable swap, but that is only a workaround. Until reiserfs gets a little lighter on caching, my recommendation is definitely xfs.

    --
    --- .tag
  86. Maybe not Slashdot itself... by Anonymous Coward · · Score: 0

    But then if they came the day people were playing with Goatse.cx Ascii Art...
    8| Gosh, that was horrible 8|

  87. My 2 cents on partitions by duckie13 · · Score: 1

    Just a quick example from myself..

    I had a server running RedHat 6.2 with a standard server setup (partitions: /, /boot, /usr, /var, /home, and swap). Well, long story short, my HDD fscked up and crashed. I could still somewhat get into it, by throwing it on my workstation, but the /usr partition was the one that had all the problems, and that's where my webpages were (/usr/local/apache/).

    So, since then, I've created a /www partition just in case of emergency. I've set mine at 50 MB, and even that seems way too big for what I'm doing (barely anyone goes to the site, but it's all for fun), but it's all precautionary - if other partitions die on me, I could (hopefully) get into the system as single user, and save my pages instead of having to redo all of them.

    --
    "My days are less enjoyable because of people." ~ Johnny the Homicidal Maniac
  88. Re:Here, Pick This One, No, Pick this one by Anonymous Coward · · Score: 0

    I am trying to find a OS that can answer an important question. Any suggestions on a Linux distribution that I can try would be appreciated.
    Question: What is the meaning of life?

  89. Re:Some other questions....Lindows by Anonymous Coward · · Score: 0

    Lindows is better than both Linux and Windows.
    And Big Macs are better than vi and Emacs combined.

  90. Partition Types? Dont he mean FS's? by Anonymous Coward · · Score: 0

    Partition types... Jesus...