1 |
On Sun, Jan 02, 2011 at 10:31:42AM +0800, William Kenworthy wrote |
2 |
|
3 |
> I use "dirvish" for backups which creates a LOT of hardlinks which can |
4 |
> be very hard on a file system. ext2 typically lasts only a few cycles, |
5 |
> while ext3 is only a little better even with full journalling. Coupled |
6 |
> to the fact neither is very good with power cuts and they are a worst |
7 |
> case choice for data security :) |
8 |
|
9 |
Am I mis-understanding or are you mis-speaking? hardlinks != backup |
10 |
A hardlink is simply another pointer to the same tracks/sectors on disk. |
11 |
If the on-disk data is destroyed it doesn't matter how many pointers you |
12 |
have to the data, it's gone. A real backup is another copy of the data |
13 |
on another drive, preferably external. |
14 |
|
15 |
> Reiserfs3 by contrast is very very good, with only a few instances of |
16 |
> problems over many years (since beore 3 was even in the kernel) - none |
17 |
> of which have lost critical data or file systems (ext2/3 devs, are you |
18 |
> listening :) |
19 |
|
20 |
I don't think ext2fs is being developed as such. And ext3fs is mostly |
21 |
a journalling system backported to ext2fs. ext2fs was written way back |
22 |
when in January 1993, and the specs were uptodate for then, but our |
23 |
expectations, and disk sizes have grown since then. |
24 |
|
25 |
> So, for me at least, btrfs is looking like the way forward. Its in |
26 |
> "testing" at the moment, but I am ready to move whole systems over |
27 |
> to it. |
28 |
|
29 |
I'm on reiserfs3 for now. Hopefully, it'll be maintained until ext4 |
30 |
or btrfs or whatever is deemed ready for primetime. When that happens, |
31 |
I'll do any new installs on the new filesystem. If it works, don't muck |
32 |
around with it. Unless support/maintenance for reiserfs3 is dropped or |
33 |
a new fs comes out with a feature I really want/need, I won't migrate |
34 |
existing systems. |
35 |
|
36 |
-- |
37 |
Walter Dnes <waltdnes@××××××××.org> |