Re: Hibernation into swap file

06.05.2019 21:25, Maksim Fomin пишет: > ‐‐‐ Original Message ‐‐‐ > On Monday, 6 May 2019 г., 8:40, Chris Murphy wrote: > >> On Sun, May 5, 2019 at 3:09 AM Andrei Borzenkov arvidj...@gmail.com wrote: >> >>> 05.05.2019 10:50, Maksim Fomin пишет: >>> Good day. Since 5.0 btrfs suppo

Re: Howto read btrfs stack trace?

On Mon, May 06, 2019 at 07:21:36PM +0300, Otto Kekäläinen wrote: > Hello! > > I attempted to run btrfs balance, but it crashed soon after start. The stack traces you provided did not occur as the result of a crash. Was there a crash after these? > Status is stuck on this: > > $ sudo btrfs balan

Re: [PATCH v3] btrfs: Flush before reflinking any extent to prevent NOCOW write falling back to CoW without data reservation

On Wed, May 8, 2019 at 1:43 PM Qu Wenruo wrote: > > [BUG] > The following script can cause unexpected fsync failure: > > #!/bin/bash > > dev=/dev/test/test > mnt=/mnt/btrfs > > mkfs.btrfs -f $dev -b 512M > /dev/null > mount $dev $mnt -o nospace_cache > > # Prealloc one extent > xfs_i

Re: [PATCH v4] fstests: generic: Test if we can still do certain operations which doesn't take data space on full fs

On Wed, May 8, 2019 at 3:04 PM Qu Wenruo wrote: > > This test will test if we can still do the following operations when a > full is full: > - buffered write into unpopulated preallocated extent > - clone the untouched preallocated extent > - fsync > - no data loss if power loss happens after abov

hello dear

Assalamu Alaikum Wa Rahmatullahi Wa Barakatuh, hello dear I came across your contact during my private search. Mrs Aisha Al- Qaddafi is my name, the only daughter of late Libyan president, am a single Mother and a Widow with three Children.I have funds the sum of $27.5 million USD for investment,

[PATCH v4] fstests: generic: Test if we can still do certain operations which doesn't take data space on full fs

This test will test if we can still do the following operations when a full is full: - buffered write into unpopulated preallocated extent - clone the untouched preallocated extent - fsync - no data loss if power loss happens after above fsync Above operations should not fail, as they takes no extr

Re: [PATCH v3] fstests: generic: Test if we can still do certain operations which doesn't take data space on full fs

On Wed, May 8, 2019 at 2:27 PM Qu Wenruo wrote: > > This test will test if we can still do the following operations when a > full is full: > - buffered write into unpopulated preallocated extent > - clone the untouched preallocated extent > - fsync > - no data loss if power loss happens after abov

Re: [PATCH] btrfs: run delayed iput at unlink time

On 8 May 2019, at 3:15, Nikolay Borisov wrote: > On 7.05.19 г. 20:27 ч., Josef Bacik wrote: >> We have been seeing issues in production where a cleaner script will >> end >> up unlinking a bunch of files that have pending iputs. This means >> they >> will get their final iput's run at btrfs-cle

[PATCH v3] fstests: generic: Test if we can still do certain operations which doesn't take data space on full fs

This test will test if we can still do the following operations when a full is full: - buffered write into unpopulated preallocated extent - clone the untouched preallocated extent - fsync - no data loss if power loss happens after above fsync Above operations should not fail, as they takes no extr

[PATCH v3] btrfs: Flush before reflinking any extent to prevent NOCOW write falling back to CoW without data reservation

[BUG] The following script can cause unexpected fsync failure: #!/bin/bash dev=/dev/test/test mnt=/mnt/btrfs mkfs.btrfs -f $dev -b 512M > /dev/null mount $dev $mnt -o nospace_cache # Prealloc one extent xfs_io -f -c "falloc 8k 64m" $mnt/file1 # Fill the remaining data space xf

Re: [PATCH v2] fstests: generic: Test if we can still do operations which don't take extra data space on a fs without data space

On 2019/5/8 下午6:38, Filipe Manana wrote: > On Wed, May 8, 2019 at 11:06 AM Qu Wenruo wrote: >> >> This test will test if we can still do the following operations when a >> fs has no extra data space: >> - buffered write into unpopulated preallocated extent >> - clone the untouched preallocated e

Re: [PATCH v2] fstests: generic: Test if we can still do operations which don't take extra data space on a fs without data space

On Wed, May 8, 2019 at 11:06 AM Qu Wenruo wrote: > > This test will test if we can still do the following operations when a > fs has no extra data space: > - buffered write into unpopulated preallocated extent > - clone the untouched preallocated extent > - fsync > Above operations in a row should

[PATCH v2] fstests: generic: Test if we can still do operations which don't take extra data space on a fs without data space

This test will test if we can still do the following operations when a fs has no extra data space: - buffered write into unpopulated preallocated extent - clone the untouched preallocated extent - fsync Above operations in a row should not fail, as they takes no extra data space. Xfs passes the te

Re: [PATCH] btrfs: Flush before reflinking any extent to prevent NOCOW write falling back to CoW without data reservation

On Wed, May 8, 2019 at 9:24 AM Qu Wenruo wrote: > > [BUG] > The following script can cause unexpected fsync failure: > > #!/bin/bash > > dev=/dev/test/test > mnt=/mnt/btrfs > > mkfs.btrfs -f $dev -b 512M > /dev/null > mount $dev $mnt -o nospace_cache > > # Prealloc one extent > xfs_i

Re: [PATCH] fstests: generic: Test if fsync will fail after NOCOW write and reflink

On Wed, May 8, 2019 at 8:48 AM Qu Wenruo wrote: > > This test case is going to check if btrfs will fail fsync after NOCOW > buffered write and reflink. > > Btrfs' back reference only has extent level granularity, so if we do > buffered write which can be done NOCOW, then reflink, that buffered > w

Re: [PATCH 2/2] Btrfs: teach tree-checker to detect file extent items with overlapping ranges

On 2019/5/6 下午11:44, fdman...@kernel.org wrote: > From: Filipe Manana > > Having file extent items with ranges that overlap each other is a serious > issue that leads to all sorts of corruptions and crashes (like a BUG_ON() > during the course of __btrfs_drop_extents() when it traims file exten

[PATCH] fstests: generic: Test if fsync will fail after NOCOW write and reflink

This test case is going to check if btrfs will fail fsync after NOCOW buffered write and reflink. Btrfs' back reference only has extent level granularity, so if we do buffered write which can be done NOCOW, then reflink, that buffered write will be forced CoW. And if we have no data space left, C

[PATCH] btrfs: Flush before reflinking any extent to prevent NOCOW write falling back to CoW without data reservation

[BUG] The following script can cause unexpected fsync failure: #!/bin/bash dev=/dev/test/test mnt=/mnt/btrfs mkfs.btrfs -f $dev -b 512M > /dev/null mount $dev $mnt -o nospace_cache # Prealloc one extent xfs_io -f -c "falloc 8k 64m" $mnt/file1 # Fill the remaining data space xf

Re: [PATCH] btrfs: run delayed iput at unlink time

On 7.05.19 г. 20:27 ч., Josef Bacik wrote: > We have been seeing issues in production where a cleaner script will end > up unlinking a bunch of files that have pending iputs. This means they > will get their final iput's run at btrfs-cleaner time and thus are not > throttled, which impacts the