Displaying 12 results from an estimated 12 matches similar to: "[PATCH] xfstests: add generic/320 to test fsync() on directories V2"
2013 Nov 15
7
[PATCH 1/2] xfstests: add generic/321 to test fsync() on directories V2
Btrfs had some issues with fsync()''ing directories and fsync()''ing after
renames. These three new tests cover the 3 different issues we were seeing.
This breaks out the dmflakey stuff into a common helper to be shared between
generic/311 and generic/321. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
---
V1->V2: rename test to generic/321
-removed an
2013 Jul 01
1
[PATCH v2] xfstests: btrfs/316: cross-subvolume sparse copy
This testscript creates reflinks to files on different subvolumes,
overwrites the original files and reflinks, and moves reflinked files
between subvolumes.
Originally submitted as testcase 302, changes are made based on comments
from Eric: http://oss.sgi.com/archives/xfs/2013-03/msg00231.html
Two new common/rc functions used in this script (_require_cp_reflink and
_verify_reflink) have been
2013 May 20
1
[PATCH] xfstests: btrfs 308: regression test for btrfs send
I''m not sure how the numbering is supposed to work now that we''ve split
everything out so I''m just going with the next number in the directory. This is
a regression test for btrfs send, we had a problem where we''d try to send a file
that had been deleted in the source snapshot. This is just to make sure we
don''t have the same problem in the future.
2013 Jul 02
6
[PATCH v3] xfstests: btrfs/316: cross-subvolume sparse copy
This testscript creates reflinks to files on different subvolumes, overwrites the original files and reflinks, and moves reflinked files between subvolumes.
Originally submitted as testcase 302, changes are made based on comments from Eric: http://oss.sgi.com/archives/xfs/2013-03/msg00231.html
Two new common/rc functions used in this script (_require_cp_reflink and _verify_reflink) have been
2013 May 03
3
[PATCH] xfstests: unmount scratch mnt in test 307
So if you have a mount command that doesn''t use /etc/mtab then it will spit out
a different device for the mounted device. So say we have
SCRATCH_DEV_POOL="/dev/sda /dev/sdb /dev/sdc"
we will turn this into
SCRATCH_DEV="/dev/sda"
SCRATCH_DEV_POOL="/dev/sdb /dev/sdc"
and then when you mkfs this you do _scratch_mkfs $SCRATCH_DEV_POOL which turns
into this
2013 Aug 16
2
[PATCH] xfstests: update filters and output of btrfs/006
The btrfs-progs tools changed the output:
- 100GiB instead of 100GB
- The number of spaces was changed
Signed-off-by: Stefan Behrens <sbehrens@giantdisaster.de>
---
common/filter | 2 +-
common/filter.btrfs | 3 ++-
tests/btrfs/006 | 6 +++---
tests/btrfs/006.out | 36 ++++++++++++++++++------------------
4 files changed, 24 insertions(+), 23 deletions(-)
diff --git
2013 Jul 02
2
[PATCH] xfstests: make the scratch device for generic/256 slightly larger
This is similar to a previous fix I sent. 1 gig makes us do mixed file block
groups for btrfs, so these enospc tests will usually fail because we don''t have
space for metadata, which is the case for this test. So jack the size up to
1.5gig so that btrfs can do its normal thing and pass the test. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
---
tests/generic/256 |
2020 Jun 18
0
[PATCH AUTOSEL 5.4 096/266] virtiofs: schedule blocking async replies in separate worker
From: Vivek Goyal <vgoyal at redhat.com>
[ Upstream commit bb737bbe48bea9854455cb61ea1dc06e92ce586c ]
In virtiofs (unlike in regular fuse) processing of async replies is
serialized. This can result in a deadlock in rare corner cases when
there's a circular dependency between the completion of two or more async
replies.
Such a deadlock can be reproduced with xfstests:generic/503 if
2020 Jun 18
0
[PATCH AUTOSEL 5.7 131/388] virtiofs: schedule blocking async replies in separate worker
From: Vivek Goyal <vgoyal at redhat.com>
[ Upstream commit bb737bbe48bea9854455cb61ea1dc06e92ce586c ]
In virtiofs (unlike in regular fuse) processing of async replies is
serialized. This can result in a deadlock in rare corner cases when
there's a circular dependency between the completion of two or more async
replies.
Such a deadlock can be reproduced with xfstests:generic/503 if
2012 Mar 12
0
Dovecot LDA breaking .qmail forwarding?
Good morning all,
I've a problem, I'm using the Dovecot LDA in my .qmail file:
|/var/qmail/bin/preline -f /usr/local/libexec/dovecot/deliver -d $EXT@$USER
However when I add a forward, such as:
|/var/qmail/bin/preline -f /usr/local/libexec/dovecot/deliver -d $EXT@$USER
<mailto:&wouter at vdschagt.com> &wouter at vdschagt.com
The mail isn't forwarded
2010 Jun 18
1
Dovecot 2.0 auth socket error
Hi Timo,
ok, when dovecot starts up, it creates the socket files in
/usr/local/var/run/dovecot for the auth and a variety of other socket
stuff you have going on. It creates these socket files with root ownership.
But I have in the config files that dovecot is running as a particular
user (in this case uid100 and gid100) to match the global mail systems
needs.
I use qmail as the delivery agent,
2008 Oct 16
3
regarding dovecot.index.cache
Hi,
This is regarding updating dovecot.index.cache.
I have few backup ids configured. these are used only when old mail
needs to be retrieved.
usually these mailboxes contains more then 9,000 mails.
while login to webmail, imap consumption is high, which creates
performance related issues for regular mailboxes.
to resolve this i have to move heavy mailbox to dedicated server.
before doing