On 2019/6/30 上午2:50, Pierre Couderc wrote:
> 1- Is there a summary of btrfs recommendations for maintenance ?
>
> I have read somewhere that a monthly btrfs scrub is recommended. Is
> there somewhere a reference, an "official" (or not...) guide of all
> that is recommended ?
I'd say scrub
Greetings!
I have a 50-Gb backup of a btrfs subvolume made with 'btrfs send
mysubvolume | pigz > mysubvolume.btrfs.gz'. Later it turned out that the
archive is damaged - there are a few consecutive gzip errors after 1 Gb.
The rest of the file can be recovered with gzip recovery tools.
However, 'b
On Sun, Jun 23, 2019 at 10:14:34AM -0400, Zygo Blaxell wrote:
> On Tue, Apr 23, 2019 at 07:06:51PM -0400, Zygo Blaxell wrote:
> > I had a test filesystem that ran out of unallocated space, then ran
> > out of metadata space during a snapshot delete, and forced readonly.
> > The workload before the
On Wed, Apr 03, 2019 at 10:47:16AM -0400, Zygo Blaxell wrote:
> On Tue, Mar 12, 2019 at 12:00:25AM -0400, Zygo Blaxell wrote:
> > On 4.14.x and 4.20.14 kernels (probably all the ones in between too,
> > but I haven't tested those), I get what I call "ghost parent transid
> > verify failed" errors.
As btrfs(5) specified:
Note
If nodatacow or nodatasum are enabled, compression is disabled.
If NODATASUM or NODATACOW set, we should not compress the extent.
Normally NODATACOW is detected properly in run_delalloc_range() so
compression won't happen for NODATACOW.
However for NO
On 2019/7/1 上午11:39, Zygo Blaxell wrote:
> On Wed, Apr 03, 2019 at 10:47:16AM -0400, Zygo Blaxell wrote:
>> On Tue, Mar 12, 2019 at 12:00:25AM -0400, Zygo Blaxell wrote:
>>> On 4.14.x and 4.20.14 kernels (probably all the ones in between too,
>>> but I haven't tested those), I get what I call "gh
