Why XFS
Motto: quoting xfs whitepaper from 1996 usenix conference: With today's 9 gigabyte disk drives it only takes 112 disk drives to surpass 1 terabyte of storage capacity (emphasis mine). http://oss.sgi.com/projects/xfs/papers/xfs_usenix/index.html
XFS: eXtended File System (SGI, Unix, Windows)
What are 'journaled filesystems': filesystems with journal.
- Good:
- Old and very well-tested: shipping since 1994
- Very good performance on large IOS
- Fully 64bit filesystem, has no problem with large files and discs, very well tested ( literaly decades ) with terabyte-range files and filesystems.
- Security: damaged files gets zeroed...
- Native quota
- Native acl
- Native EAs
- Bad:
- Relatively new to linux. But still - oldest journaling filesystem available on Linux
- Slow on small files ( with 1-2k sized files even ext2 is way faster)
- Convenience: damaged files gets zeroed... supposedly this is the issue with all journaling filesystems
- Not very popular - issues with exotic software: quotes inside virtual servers, etc..
- Not very simple codebase, stable and well-tested, but very big and relatively intrusive. (non-issue on 2.6, where lots of needed support was moved to lower layers, things like variable-size IO requests, delayed allocation )
- Takes few % more of diskspace then others, it bit me when I tried to convert partition that was 99% full...
- On related note - xfs is very slow when filesystem is 99.x% full,
- No
data=journal - You can't use it in raid1 both driectly on hardware and via md1
| Why XFS | | 2004.05.03-21:07.00
Running with VPNs...
- ppp+ssh
- IPSec - FreeS/WAN
- pptp
- openvpn
- cipe
- ?tinc?
- http://amvpn.sf.net Amrita VPN (ssl-based)
- http://htun.runslinux.net HTun - tunnelling via http
| Running with VPNs... | | 2004.02.17-15:09.00
