This tests is most similar to xfstests generic/405.
It calls device mapper to create a thin provision device with small
backing size and big virtual size. mkfs.btrfs should fail on such
devices.
This test should pass after commit e805b143a4fe
("btrfs-progs: mkfs: return nozero value on thin provis
Variable do_wait is synchronized with the variable do_background,
when if(do_background) is true, if(!do_wait) is also true, so parent
process will goto out immediately. The following wait never be run.
And if option -B is chosen, when do_background is 0 and do_wait is 1,
there is no need to fork
Variable do_wait is synchronized with the variable do_background,
when if(do_background) is true, if(!do_wait) is also true, so parent
process will goto out immediately. The following wait never be run.
And if option -B is chosen, when do_background is 0 and do_wait is 1,
there is no need to fork
Change the behaior of rmdir(2) and allow it to delete an empty subvolume
by calling btrfs_delete_subvolume() which is used by
btrfs_ioctl_snap_destroy(). The required lock for @dir and inode of
@dentry is already acquired in vfs layer.
We need some check before deleting a subvolume. Permission che
Use btrfs_delete_subvolume() to refactor btrfs_ioctl_snap_destroy().
The permission check is still done in btrfs_ioctl_snap_destroy(). Also,
call of d_delete() is still required since btrfs_delete_subvolume()
does not call it.
As a result, btrfs_unlink_subvol() and may_destroy_subvol()
become stat
Add new function btrfs_delete_subvolume() which is almost identical
to the secand half of btrfs_ioctl_snap_destroy(). This function requires
inode_lock for both @dir and inode of @dentry.
This performes additional check (1. send is not in progress. 2. the
subvolume is not a default subvolume. 3. t
This is a preparation work to refactor btrfs_ioctl_snap_destroy()
and to allow rmdir(2) to delete an empty subvolume.
Signed-off-by: Tomohiro Misono
---
fs/btrfs/ctree.h | 1 +
fs/btrfs/inode.c | 54 ++
fs/btrfs/ioctl.c | 54 --
changelog:
v3 -> v4 ... Reorganize patches and updates commit log.
No code change in total
v2 -> v3 ... Use if-else block instead of two if blocks and
add Tested-by tag in 2nd patch
v1 -> v2 ... Split the patch to hopefully make review easier
Note: I will send
On 2018/04/06 23:46, David Sterba wrote:
> On Fri, Mar 30, 2018 at 03:16:47PM +0900, Misono Tomohiro wrote:
>> This patch changes the behavior of rmdir(2) to allow it to delete
>> an empty subvolume by default, unless it is not a default subvolume
>> and send is not in progress.
>>
>> New function
On 2018年04月11日 05:04, Goffredo Baroncelli wrote:
> Hi Qu,
>
> On 04/10/2018 04:00 AM, Qu Wenruo wrote:
>>
>>
>> On 2018年04月10日 05:50, Goffredo Baroncelli wrote:
>>> Hi Qu,
>>>
>>> On 04/09/2018 11:19 AM, Qu Wenruo wrote:
When manually patching super blocks, current validation check is prett
Hello,
My name is Hon. Ms. Reem Al-Hashimy I am the present Ministry of petroleum in
UAE. I write to solicit for your partnership in claiming of $47 Million USD
from a Financial Home in Uk.
The aforementioned fund $47 Million USD is my share percentage from a Oil
companies that I helped financ
Hi Qu,
On 04/10/2018 04:00 AM, Qu Wenruo wrote:
>
>
> On 2018年04月10日 05:50, Goffredo Baroncelli wrote:
>> Hi Qu,
>>
>> On 04/09/2018 11:19 AM, Qu Wenruo wrote:
>>> When manually patching super blocks, current validation check is pretty
>>> weak (limited to magic number and csum) and doesn't prov
Add libbtrfsutil objects to btrfs.static link command. This fixes static
build failure:
utils.static.o: In function `parse_qgroupid':
utils.c:(.text.parse_qgroupid+0xb0): undefined reference to
`btrfs_util_is_subvolume'
props.static.o: In function `prop_read_only':
props.c:(.text.prop_read_only+0
On Mon, Mar 19, 2018 at 04:27:09PM +0900, Misono, Tomohiro wrote:
> changelog:
>
> v2-> v3
> - fix kbuild test bot warning
> v1 -> v2
> - completely reimplement 1st/2nd ioctl to have user friendly api
> - various cleanup, remove unnecessary goto
> ===
>
> This adds three new unprivileged ioc
On Fri, Nov 17, 2017 at 11:44:47AM -0600, Goldwyn Rodrigues wrote:
> From: Goldwyn Rodrigues
>
> Preparatory patch. It reduces the arguments to __btrfs_buffered_write
> to follow buffered_write() style.
>
> Signed-off-by: Goldwyn Rodrigues
I got pointed to this patch that it could be applied i
On Thu, Feb 22, 2018 at 06:12:14PM +0200, Nikolay Borisov wrote:
> Now that the read side is extracted into its own function, do the same
> to the write side. This leaves btrfs_get_blocks_direct_write with the
> sole purpose of handling common locking required. Also flip the
> condition in btrfs_ge
On Thu, Feb 22, 2018 at 06:12:13PM +0200, Nikolay Borisov wrote:
> Currently this function handles both the READ and WRITE dio cases. This
> is facilitated by a bunch of 'if' statements, a goto short-circuit
> statement and a very perverse aliasing of "!created"(READ) case
> by setting lockstart =
On Fri, Mar 30, 2018 at 08:09:16AM +0800, Anand Jain wrote:
> v3->v4:
> Update changelog and signoff.
> Reintroduce explicit check for '-EUCLEAN'
> at Patch 2/8 and 5/8.
>
> v2->v3:
> Squash
> 4/8 btrfs: make btrfs_check_super_csum() non static
> to
> 6/8 btrfs: verify superblock checksu
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: c71bf099abdd Btrfs: Avoid orphan inodes cleanup while replaying
log.
The bot has also determined it's probably a bug fixing patch. (score: 6.2138)
The bot has tested the following
On 2018-04-10 09:08, James Courtier-Dutton wrote:
Hi,
I have disk that in the past had errors on it.
I have fixed up the errors.
btrfs scrub now reports no errors.
How do I reset these counters to zero?
BTRFS info (device sdc2): bdev /dev/sdc2 errs: wr 0, rd 35, flush 0,
corrupt 1, gen 0
Run
Hi,
I have disk that in the past had errors on it.
I have fixed up the errors.
btrfs scrub now reports no errors.
How do I reset these counters to zero?
BTRFS info (device sdc2): bdev /dev/sdc2 errs: wr 0, rd 35, flush 0,
corrupt 1, gen 0
Kind Regards
James
--
To unsubscribe from this list:
On Mon, Apr 09, 2018 at 06:23:14PM -0700, Liu Bo wrote:
> >>> As maybe_insert_hole is only called by btrfs_cont_expand here, which
> >>> means it's a really hole, I don't expect drop_extents would drop
> >>> anything, we can remove this drop_extents and put an assert after
> >>> btrfs_insert_file_e
On Tue, Apr 10, 2018 at 10:45:39AM +0300, Nikolay Borisov wrote:
> On 9.04.2018 14:58, David Sterba wrote:
> > We really want to know to which filesystem the extent map events belong,
> > but as it cannot be reached from the extent_map pointers, we need to
> > pass it down the callchain.
>
> I re
On 9.04.2018 14:58, David Sterba wrote:
> Switch the inode number type to u64, plus other cleanups and fixups.
>
> David Sterba (7):
> btrfs: tracepoints, use correct type for inode number
> btrfs: tracepoints, use %llu instead of %Lu
> btrfs: tracepoints, drop unnecessary ULL casts
> b
On 9.04.2018 14:58, David Sterba wrote:
> We really want to know to which filesystem the extent map events belong,
> but as it cannot be reached from the extent_map pointers, we need to
> pass it down the callchain.
I really dislike propagating arguments solely for tracepoints purposes,
but if
25 matches
Mail list logo