| To: | Alexander Tsvetkov <alexander.tsvetkov@xxxxxxxxxx>, Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: maxpct option for small xfs filesystems |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Wed, 28 Jan 2015 12:05:27 -0600 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <54C8BCEC.5050101@xxxxxxxxxx> |
| References: | <54C667F3.8040303@xxxxxxxxxx> <20150126223715.GA7621@dastard> <54C7BB78.4060203@xxxxxxxxxx> <54C7BD60.5000104@xxxxxxxxxxx> <54C8BCEC.5050101@xxxxxxxxxx> |
On 1/28/15 4:41 AM, Alexander Tsvetkov wrote: > What is expected behaviour in this case when it's required for fs to allocate > new inodes starting to exceed defined maxpct > percentage? Which error is expected to be returned to user, enospc or > probably just some warning? Sorry, I didn't answer this. ENOSPC is expected. There's not a lot of value in enforcing this strictly to the last inode, because a % is fairly coarse anyway, but we should not blow right past it as we do today. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: maxpct option for small xfs filesystems, Eric Sandeen |
|---|---|
| Next by Date: | Re: [PATCH 2/2] xfs_spaceman: Accounting for AGFL blocks, Dave Chinner |
| Previous by Thread: | Re: maxpct option for small xfs filesystems, Eric Sandeen |
| Next by Thread: | [PATCH 0/9] xfs: xfs_ioctl_setxattr rework, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |