Linux filesystems recoverability
up vote
0
down vote
favorite
I am on Debian 8.6 and have 1x 4 member RAID6 2TB size in effect. Apart from backup system I now need to decide what filesystem to use.
The purpose of this array is reliability, availability, and the possibility to recover deleted files.
filesystems data-recovery
edited Nov 24 at 19:39
Rui F Ribeiro
38.3k1476127
asked Oct 29 '16 at 11:31
Vlastimil
7,4471158132
add a comment |
up vote
0
down vote
favorite
I am on Debian 8.6 and have 1x 4 member RAID6 2TB size in effect. Apart from backup system I now need to decide what filesystem to use.
The purpose of this array is reliability, availability, and the possibility to recover deleted files.
filesystems data-recovery
edited Nov 24 at 19:39
Rui F Ribeiro
38.3k1476127
asked Oct 29 '16 at 11:31
Vlastimil
7,4471158132
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am on Debian 8.6 and have 1x 4 member RAID6 2TB size in effect. Apart from backup system I now need to decide what filesystem to use.
The purpose of this array is reliability, availability, and the possibility to recover deleted files.
filesystems data-recovery
edited Nov 24 at 19:39
Rui F Ribeiro
38.3k1476127
asked Oct 29 '16 at 11:31
Vlastimil
7,4471158132
I am on Debian 8.6 and have 1x 4 member RAID6 2TB size in effect. Apart from backup system I now need to decide what filesystem to use.
The purpose of this array is reliability, availability, and the possibility to recover deleted files.
filesystems data-recovery
filesystems data-recovery
edited Nov 24 at 19:39
Rui F Ribeiro
38.3k1476127
asked Oct 29 '16 at 11:31
Vlastimil
7,4471158132
edited Nov 24 at 19:39
Rui F Ribeiro
38.3k1476127
asked Oct 29 '16 at 11:31
Vlastimil
7,4471158132
edited Nov 24 at 19:39
Rui F Ribeiro
38.3k1476127
edited Nov 24 at 19:39
Rui F Ribeiro
38.3k1476127
edited Nov 24 at 19:39
Rui F Ribeiro
38.3k1476127
38.3k1476127
asked Oct 29 '16 at 11:31
Vlastimil
7,4471158132
asked Oct 29 '16 at 11:31
Vlastimil
7,4471158132
asked Oct 29 '16 at 11:31
Vlastimil
7,4471158132
7,4471158132
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
accepted
Use ext4.
The mature (and not stale) choices are basically ext4 and xfs. Redhat like XFS for it's scalability, performance. I have nothing against it but ext4 is more commonly used and hence slightly better understood (community documentation like StackExchange).
Don't expect to recover unlinked files.
There used to be an undeleter for linux ext2. There isn't one that works for modern filesystems, in my experience.
(When the FAT filesystem on your camera breaks with much-wanted photos on it - or you accidentally delete all - photorec is amazing. It works for many document types, not just photos. But you don't want to run it the server of a small business, it can't exclude files which are not deleted and it can't tell the filename).
New-fangled copy-on-write filesystems can carry historical snapshots, allowing recovery if you delete a file that existed in the last snapshot. But:
btrfs is not considered stable in Debian. (Everyone tells you to use the latest upstream kernel for btrfs, or possibly a distribution like SUSE where they were backporting fixes). btrfs' nascent native raid5/6 code was recently discovered to be broken and AFAIK still needs rewriting.
ZFS would be a valid solution. But since you don't mention it yourself, I would not suggest it. It is not even included in Debian. ZFS is kind of its own thing... it even has it's own weird cache system separate from the normal Linux VFS.
answered Oct 29 '16 at 17:27
sourcejedi
22.1k43397
add a comment |
up vote
0
down vote
This might not be the answer you want to hear but... As far as I know, there is currently no filesystem that can recover deleted files in a reliable way. I say "reliable" because I know there are tools available that claim do this, to some extent.
The only foolproof way to recover accidentally deleted files is via backups.
My suggestion is that you, instead of looking for a filesystem that can recover files, make sure that you know which data you want to back up, and do so regularly using whatever tool suits you best (I rely heavily on rsync but there are plenty of other backup tools available).
answered Oct 29 '16 at 16:11
maulinglawns
6,16621225
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Use ext4.
The mature (and not stale) choices are basically ext4 and xfs. Redhat like XFS for it's scalability, performance. I have nothing against it but ext4 is more commonly used and hence slightly better understood (community documentation like StackExchange).
Don't expect to recover unlinked files.
There used to be an undeleter for linux ext2. There isn't one that works for modern filesystems, in my experience.
(When the FAT filesystem on your camera breaks with much-wanted photos on it - or you accidentally delete all - photorec is amazing. It works for many document types, not just photos. But you don't want to run it the server of a small business, it can't exclude files which are not deleted and it can't tell the filename).
New-fangled copy-on-write filesystems can carry historical snapshots, allowing recovery if you delete a file that existed in the last snapshot. But:
btrfs is not considered stable in Debian. (Everyone tells you to use the latest upstream kernel for btrfs, or possibly a distribution like SUSE where they were backporting fixes). btrfs' nascent native raid5/6 code was recently discovered to be broken and AFAIK still needs rewriting.
ZFS would be a valid solution. But since you don't mention it yourself, I would not suggest it. It is not even included in Debian. ZFS is kind of its own thing... it even has it's own weird cache system separate from the normal Linux VFS.
answered Oct 29 '16 at 17:27
sourcejedi
22.1k43397
add a comment |
up vote
1
down vote
accepted
Use ext4.
The mature (and not stale) choices are basically ext4 and xfs. Redhat like XFS for it's scalability, performance. I have nothing against it but ext4 is more commonly used and hence slightly better understood (community documentation like StackExchange).
Don't expect to recover unlinked files.
There used to be an undeleter for linux ext2. There isn't one that works for modern filesystems, in my experience.
(When the FAT filesystem on your camera breaks with much-wanted photos on it - or you accidentally delete all - photorec is amazing. It works for many document types, not just photos. But you don't want to run it the server of a small business, it can't exclude files which are not deleted and it can't tell the filename).
New-fangled copy-on-write filesystems can carry historical snapshots, allowing recovery if you delete a file that existed in the last snapshot. But:
btrfs is not considered stable in Debian. (Everyone tells you to use the latest upstream kernel for btrfs, or possibly a distribution like SUSE where they were backporting fixes). btrfs' nascent native raid5/6 code was recently discovered to be broken and AFAIK still needs rewriting.
ZFS would be a valid solution. But since you don't mention it yourself, I would not suggest it. It is not even included in Debian. ZFS is kind of its own thing... it even has it's own weird cache system separate from the normal Linux VFS.
answered Oct 29 '16 at 17:27
sourcejedi
22.1k43397
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Use ext4.
The mature (and not stale) choices are basically ext4 and xfs. Redhat like XFS for it's scalability, performance. I have nothing against it but ext4 is more commonly used and hence slightly better understood (community documentation like StackExchange).
Don't expect to recover unlinked files.
There used to be an undeleter for linux ext2. There isn't one that works for modern filesystems, in my experience.
(When the FAT filesystem on your camera breaks with much-wanted photos on it - or you accidentally delete all - photorec is amazing. It works for many document types, not just photos. But you don't want to run it the server of a small business, it can't exclude files which are not deleted and it can't tell the filename).
New-fangled copy-on-write filesystems can carry historical snapshots, allowing recovery if you delete a file that existed in the last snapshot. But:
btrfs is not considered stable in Debian. (Everyone tells you to use the latest upstream kernel for btrfs, or possibly a distribution like SUSE where they were backporting fixes). btrfs' nascent native raid5/6 code was recently discovered to be broken and AFAIK still needs rewriting.
ZFS would be a valid solution. But since you don't mention it yourself, I would not suggest it. It is not even included in Debian. ZFS is kind of its own thing... it even has it's own weird cache system separate from the normal Linux VFS.
answered Oct 29 '16 at 17:27
sourcejedi
22.1k43397
Use ext4.
The mature (and not stale) choices are basically ext4 and xfs. Redhat like XFS for it's scalability, performance. I have nothing against it but ext4 is more commonly used and hence slightly better understood (community documentation like StackExchange).
Don't expect to recover unlinked files.
There used to be an undeleter for linux ext2. There isn't one that works for modern filesystems, in my experience.
(When the FAT filesystem on your camera breaks with much-wanted photos on it - or you accidentally delete all - photorec is amazing. It works for many document types, not just photos. But you don't want to run it the server of a small business, it can't exclude files which are not deleted and it can't tell the filename).
New-fangled copy-on-write filesystems can carry historical snapshots, allowing recovery if you delete a file that existed in the last snapshot. But:
btrfs is not considered stable in Debian. (Everyone tells you to use the latest upstream kernel for btrfs, or possibly a distribution like SUSE where they were backporting fixes). btrfs' nascent native raid5/6 code was recently discovered to be broken and AFAIK still needs rewriting.
ZFS would be a valid solution. But since you don't mention it yourself, I would not suggest it. It is not even included in Debian. ZFS is kind of its own thing... it even has it's own weird cache system separate from the normal Linux VFS.
answered Oct 29 '16 at 17:27
sourcejedi
22.1k43397
answered Oct 29 '16 at 17:27
sourcejedi
22.1k43397
answered Oct 29 '16 at 17:27
sourcejedi
22.1k43397
answered Oct 29 '16 at 17:27
sourcejedi
22.1k43397
22.1k43397
add a comment |
add a comment |
up vote
0
down vote
This might not be the answer you want to hear but... As far as I know, there is currently no filesystem that can recover deleted files in a reliable way. I say "reliable" because I know there are tools available that claim do this, to some extent.
The only foolproof way to recover accidentally deleted files is via backups.
My suggestion is that you, instead of looking for a filesystem that can recover files, make sure that you know which data you want to back up, and do so regularly using whatever tool suits you best (I rely heavily on rsync but there are plenty of other backup tools available).
answered Oct 29 '16 at 16:11
maulinglawns
6,16621225
add a comment |
up vote
0
down vote
This might not be the answer you want to hear but... As far as I know, there is currently no filesystem that can recover deleted files in a reliable way. I say "reliable" because I know there are tools available that claim do this, to some extent.
The only foolproof way to recover accidentally deleted files is via backups.
My suggestion is that you, instead of looking for a filesystem that can recover files, make sure that you know which data you want to back up, and do so regularly using whatever tool suits you best (I rely heavily on rsync but there are plenty of other backup tools available).
answered Oct 29 '16 at 16:11
maulinglawns
6,16621225
add a comment |
up vote
0
down vote
up vote
0
down vote
This might not be the answer you want to hear but... As far as I know, there is currently no filesystem that can recover deleted files in a reliable way. I say "reliable" because I know there are tools available that claim do this, to some extent.
The only foolproof way to recover accidentally deleted files is via backups.
My suggestion is that you, instead of looking for a filesystem that can recover files, make sure that you know which data you want to back up, and do so regularly using whatever tool suits you best (I rely heavily on rsync but there are plenty of other backup tools available).
answered Oct 29 '16 at 16:11
maulinglawns
6,16621225
This might not be the answer you want to hear but... As far as I know, there is currently no filesystem that can recover deleted files in a reliable way. I say "reliable" because I know there are tools available that claim do this, to some extent.
The only foolproof way to recover accidentally deleted files is via backups.
My suggestion is that you, instead of looking for a filesystem that can recover files, make sure that you know which data you want to back up, and do so regularly using whatever tool suits you best (I rely heavily on rsync but there are plenty of other backup tools available).
answered Oct 29 '16 at 16:11
maulinglawns
6,16621225
edited Oct 29 '16 at 16:23
answered Oct 29 '16 at 16:11
maulinglawns
6,16621225
answered Oct 29 '16 at 16:11
maulinglawns
6,16621225
answered Oct 29 '16 at 16:11
maulinglawns
6,16621225
6,16621225
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f319703%2flinux-filesystems-recoverability%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
