| To: | "Darrick J. Wong" <darrick.wong@xxxxxxxxxx> |
|---|---|
| Subject: | Re: block allocations for the refcount btree |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Thu, 3 Mar 2016 06:05:56 -0800 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20160302212101.GF27973@xxxxxxxxxxxxxxxx> |
| References: | <20160210190738.GA13051@xxxxxxxxxxxxx> <20160210214058.GN14668@dastard> <20160212191046.GA28421@xxxxxxxxxxxxx> <20160301181809.GC27973@xxxxxxxxxxxxxxxx> <20160301204013.GA23128@xxxxxxxxxxxxx> <20160302052411.GB1902@xxxxxxxxxxxxxxxx> <20160302095932.GA9141@xxxxxxxxxxxxx> <20160302164102.GA20109@xxxxxxxxxxxxxxxx> <20160302165704.GA31438@xxxxxxxxxxxxx> <20160302212101.GF27973@xxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.24 (2015-08-30) |
On Wed, Mar 02, 2016 at 01:21:01PM -0800, Darrick J. Wong wrote: > Ok. I think the problem is that making changes to the refcount btree eats > up our entire reservation in certain cases. Can you try the following > bandaid? > This should give us enough room to handle splitting the btree at both ends > of a range that we're refcount-changing. This seems to work in general. I ran into one log related hang when running -g auto on nfs, but it's not been reproducible so far. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH 0/4] only run torn log write detection on dirty logs, Brian Foster |
|---|---|
| Next by Date: | Re: [PATCH 1/3] xfs: build bios directly in xfs_add_to_ioend, Brian Foster |
| Previous by Thread: | Re: block allocations for the refcount btree, Darrick J. Wong |
| Next by Thread: | Re: block allocations for the refcount btree, Darrick J. Wong |
| Indexes: | [Date] [Thread] [Top] [All Lists] |