Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ZFS on Linux: Unlistable and disappearing files

github.com

Post reply on HN
Print view View original

41–50 of 168 posts

Re: ZFS on Linux: Unlistable and disappearing files

#42

Post by antongribok »

ryao wrote: post #9

We are working on it. We know what patch introduced the regression and 0.7.8 is going out soon to revert it. Until then, users should downgrade to 0.7.6 if they have not already. The Gentoo and EPEL maintainers have pulled the affected releases from the repositories (technically masked on Gentoo). Ubuntu was never affected. The regression makes it so that creating a new file could fail with ENOSPC after which files c…

This is a good reminder for everyone that snapshots are not backups.

Also, thank you for all of the hard work on ZoL!

Re: ZFS on Linux: Unlistable and disappearing files

#43

Post by gst »

Arbalest wrote: post #33
beedogs wrote: post #21

At least it's no btrfs. What a disaster that filesystem's been.

A disaster for enterprise perhaps. I use only a subset of features (such as subvolumes and snapshots and a little RAID 1) and have never had problems. With the way some people talk about it, it sure sounds like it never worked at all.

Same here. I've been using btrfs for years so far on my personal laptop and never had any problems.

Re: ZFS on Linux: Unlistable and disappearing files

#44

Post by ryao »

antongribok wrote: post #42
ryao wrote: post #9

We are working on it. We know what patch introduced the regression and 0.7.8 is going out soon to revert it. Until then, users should downgrade to 0.7.6 if they have not already. The Gentoo and EPEL maintainers have pulled the affected releases from the repositories (technically masked on Gentoo). Ubuntu was never affected. The regression makes it so that creating a new file could fail with ENOSPC after which files c…

This is a good reminder for everyone that snapshots are not backups. Also, thank you for all of the hard work on ZoL!

You are welcome.

I should clarify the snapshots remark. The problem with how this interacts with snapshots is that the snapshots containing orphaned files cannot be repaired by software without BPR. They can only be listed by software for deletion by the administrator. Also, for the dataset’s tip, the future tool to repair it can only put the orphaned files into a lost+found directory without the original file names.

Re: ZFS on Linux: Unlistable and disappearing files

#45

Post by luke0016 »

ryao wrote: post #38
luke0016 wrote: post #35

Earlier quoted context omitted.

I understand - what I meant to say is that I cannot be sure that the array never ran into an ENOSPC issue prior to the snapshot. Given that, should I keep the old array around until I can do whatever is recommended to detect potential orphans resulting from the bug? Edit: And thank you, again.

There is no reason to do that here. Send/recv makes a perfect copy as far as this is concerned. You are welcome. Also, the proper term is pool.

I come from many years of mdadm use, sorry :-)

Just so I understand, I should be able to run through whatever the final recommendation is for detecting orphans on the new pool with identical results as if it were run on the original pool, then?

Re: ZFS on Linux: Unlistable and disappearing files

#46

Post by ryao »

rhabarba wrote: post #41

So this is not a "ZFS bug", but a "ZFS on Linux" bug. The actual ZFS on systems which have had ZFS for decades is not affected at all.

It is a recent regression from 2 months ago that originated in the Linux port. I do not know the status of the other platforms. I and the others involved with the Linux port are still busy handling the issue. I suggest asking the developers of the other platforms whether they had adopted the bad patch or not.

Re: ZFS on Linux: Unlistable and disappearing files

#47

Post by [deleted] »

loeg wrote: post #14
aidenn0 wrote: post #13

Earlier quoted context omitted.

Are you still using ext2 then? Ext3 was 2001, and ZFS was 2005. JFS2 is only 19 years old so doesn't quite meet the "decades" requirement.

And just to round it out, UFS2 was first in a release in 2003 in FreeBSD 5.0. So on the BSDs you're stuck with UFS1 at "decades."

[deleted]

Re: ZFS on Linux: Unlistable and disappearing files

#49

Post by Spivak »

clircle wrote: post #26
beedogs wrote: post #21

At least it's no btrfs. What a disaster that filesystem's been.

Is there a stable (loaded word, I know) versioning file system available for Linux?

The most stable solution right now is taking your favorite stable fs like ext4 or xfs and using LVM thin pools for snapshots.

Re: ZFS on Linux: Unlistable and disappearing files

#50

Post by ryao »

luke0016 wrote: post #45
ryao wrote: post #38

Earlier quoted context omitted.

There is no reason to do that here. Send/recv makes a perfect copy as far as this is concerned. You are welcome. Also, the proper term is pool.

I come from many years of mdadm use, sorry :-) Just so I understand, I should be able to run through whatever the final recommendation is for detecting orphans on the new pool with identical results as if it were run on the original pool, then?

Yes.
Post reply on HN