Displaying 20 results from an estimated 500 matches similar to: "Error on creating snapshots (btrfs: could not do orphan cleanup -116)"
2011 Sep 21
3
[PATCH] Btrfs: fix orphan cleanup regression
In fixing how we deal with bad inodes, we had a regression in the orphan cleanup
code, since it expects to get a bad inode back. So fix it to deal with getting
-ESTALE back by deleting the orphan item manually and moving on. Thanks,
Reported-by: Simon Kirby <sim@hostway.ca>
Signed-off-by: Josef Bacik <josef@redhat.com>
---
fs/btrfs/inode.c | 36
2011 Oct 04
3
[PATCH] Btrfs: break out of orphan cleanup if we can't make progress V2
I noticed while running xfstests 83 that if we didn''t have enough space to
delete our inode the orphan cleanup would just loop. This is because it keeps
finding the same orphan item and keeps trying to kill it but can''t because we
don''t get an error back from iput for deleting the inode. So keep track of the
last guy we tried to kill, if it''s the same as the
2008 Jul 20
26
[PATCH] NFS support for btrfs - v2
Hi,
Here''s an implementation of NFS support for btrfs. It does not work in one
particular case as described in
http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg00298.html.
This uses the btrfs_iget helper introduced previously.
Comments ?
---
Signed-off-by: Balaji Rao <balajirrao@gmail.com>
diff -r 3f0eee804974 Makefile
--- a/Makefile Thu Jun 26 10:34:20 2008 -0400
2012 Jan 05
4
[RFC][PATCH 3/3] Btrfs: improve truncation of btrfs
The original truncation of btrfs has a bug, that is the orphan item will not be
dropped when the truncation fails. This bug will trigger BUG() when unlink that
truncated file. And besides that, if the user does pre-allocation for the file
which is truncated unsuccessfully, after re-mount(umount-mount, not -o remount),
the pre-allocated extent will be dropped.
This patch modified the relative
2012 Apr 20
44
Ceph on btrfs 3.4rc
After running ceph on XFS for some time, I decided to try btrfs again.
Performance with the current "for-linux-min" branch and big metadata
is much better. The only problem (?) I''m still seeing is a warning
that seems to occur from time to time:
[87703.784552] ------------[ cut here ]------------
[87703.789759] WARNING: at fs/btrfs/inode.c:2103
2012 Sep 17
13
[PATCH 1/2 v3] Btrfs: use flag EXTENT_DEFRAG for snapshot-aware defrag
We''re going to use this flag EXTENT_DEFRAG to indicate which range
belongs to defragment so that we can implement snapshow-aware defrag:
We set the EXTENT_DEFRAG flag when dirtying the extents that need
defragmented, so later on writeback thread can differentiate between
normal writeback and writeback started by defragmentation.
This patch is used for the latter one.
Originally patch
2011 Jul 21
10
[PATCH v5 0/8] Btrfs scrub: print path to corrupted files and trigger nodatasum fixup
While testing raid-auto-repair patches I''m going to send out later, I just found
the very last bug in my current scrub patch series:
Changelog v4->v5:
- fixed a deadlock when fixup is taking longer while scrub is about to end
Original message follows:
------------------------
This patch set introduces two new features for scrub. They share the backref
iteration code which is the
2010 Jan 15
0
[PATCH] Btrfs: fix regression in orphan cleanup
Currently orphan cleanup only ever gets triggered if we cross subvolumes during
a lookup, which means that if we just mount a plain jane fs that has orphans in
it, they will never get cleaned up. This results in panic''s like these
http://www.kerneloops.org/oops.php?number=1109085
where adding an orphan entry results in -EEXIST being returned and we panic. In
order to fix this, we
2008 Aug 30
0
[PATCH] btrfs: remove unused function btrfs_ilookup
btrfs_ilookup is unused, which is good because a normal filesystem
should never have to use ilookup anyway. Remove it.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: btrfs-unstable/ctree.h
===================================================================
--- btrfs-unstable.orig/ctree.h 2008-08-30 11:08:58.000000000 -0300
+++ btrfs-unstable/ctree.h 2008-08-30 11:09:10.000000000
2008 Jun 24
1
[RFC][PATCH] btrfs orphan code
Hello,
I want to throw this out here now that I''ve got most of the heavy lifting done
for this code to make sure what I''m doing is ok for now. I''ve added an
ORPHAN_DIR item key to have a hidden dir per root. Right now it just does it
for whatever the default root is on mount, but I''m going to fix that to do the
orphan dir check/creation on lookup of a
2011 May 11
8
[PATCH 1/4] Btrfs: map the node block when looking for readahead targets
If we have particularly full nodes, we could call btrfs_node_blockptr up to 32
times, which is 32 pairs of kmap/kunmap, which _sucks_. So go ahead and map the
extent buffer while we look for readahead targets. Thanks,
Signed-off-by: Josef Bacik <josef@redhat.com>
---
fs/btrfs/ctree.c | 23 +++++++++++++++++++++--
1 files changed, 21 insertions(+), 2 deletions(-)
diff --git
2011 Jun 21
19
[GIT PULL v3] Btrfs: improve write ahead log with sub transaction
I''ve been working to try to improve the write-ahead log''s performance,
and I found that the bottleneck addresses in the checksum items,
especially when we want to make a random write on a large file, e.g a 4G file.
Then a idea for this suggested by Chris is to use sub transaction ids and just
to log the part of inode that had changed since either the last log commit or
the last
2001 Mar 05
2
Samba on vxfs
Has anyone had any experience with samba on a Solaris 2.6 system using
vxfs file system?
2013 Feb 07
1
[PATCH] Btrfs: cleanup orphan reservation if truncate fails
I noticed we were getting lots of warnings with xfstest 83 because we have
reservations outstanding. This is because we moved the orphan add outside
of the truncate, but we don''t actually cleanup our reservation if something
fails. This fixes the problem and I no longer see warnings. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
---
fs/btrfs/inode.c | 2 ++
1
2012 Apr 09
9
[PATCH] Btrfs: use i_version instead of our own sequence
We''ve been keeping around the inode sequence number in hopes that somebody
would use it, but nobody uses it and people actually use i_version which
serves the same purpose, so use i_version where we used the incore inode''s
sequence number and that way the sequence is updated properly across the
board, and not just in file write. Thanks,
Signed-off-by: Josef Bacik
2011 Aug 23
40
[PATCH 00/21] [RFC] Btrfs: restriper
Hello,
This patch series adds an initial implementation of restriper (it''s a
clever name for relocation framework that allows to do selective profile
changing and selective balancing with some goodies like pausing/resuming
and reporting progress to the user.
Profile changing is global (per-FS) so far, per-subvolume profiles
require some discussion and can be implemented in future.
2013 Aug 02
2
[PATCH] Btrfs: allow compressed extents to be merged during defragment
The rule originally comes from nocow writing, but snapshot-aware
defrag is a different case, the extent has been writen and we''re
not going to change the extent but add a reference on the data.
So we''re able to allow such compressed extents to be merged into
one bigger extent if they''re pointing to the same data.
Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
---
2008 Aug 28
0
[PATCH] btrfs: cleanup d_obtain_alias useage
d_obtain_alias is intended as a tailcall that can pass in errors encoded
in the inode pointer if needed, so use it that way instead of
duplicating the error handling.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: btrfs-unstable/export.c
===================================================================
--- btrfs-unstable.orig/export.c 2008-08-28 19:56:13.000000000 -0300
+++
2001 Aug 13
0
(no subject)
>From nfs-admin@lists.sourceforge.net Thu Feb 1 03:51:36 2001
>Return-Path: <nfs-admin@lists.sourceforge.net>
Received: from usw-sf-list1.sourceforge.net (usw-outbound.sourceforge.net [216.136.171.194])
by gateway.camelot.jp (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id DAA11596
for <jareth@camelot.co.jp>; Thu, 1 Feb 2001 03:51:35 +0900
X-Authentication-Warning:
2011 Aug 15
9
[patch v2 0/9] btrfs: More error handling patches
Hi all -
The following 9 patches add more error handling to the btrfs code:
- Add btrfs_panic
- Catch locking failures in {set,clear}_extent_bit
- Push up set_extent_bit errors to callers
- Push up lock_extent errors to callers
- Push up clear_extent_bit errors to callers
- Push up unlock_extent errors to callers
- Make pin_down_extent return void
- Push up btrfs_pin_extent errors to