|Subject:||Re: xfs_fsr, sunit, and swidth|
|From:||Dave Hall <kdhall@xxxxxxxxxxxxxx>|
|Date:||Mon, 15 Apr 2013 16:35:38 -0400|
|Cc:||"xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>, Dave Chinner <david@xxxxxxxxxxxxx>|
|References:||<5141C1FC.4060209@xxxxxxxxxxxxxxxxx> <5141C8C1.2080903@xxxxxxxxxxxxxxxxx> <5141E5CF.10101@xxxxxxxxxxxxxx> <5142AE40.6040408@xxxxxxxxxxxxxxxxx> <20130315114538.GF6369@dastard> <5143F94C.1020708@xxxxxxxxxxxxxxxxx> <20130316072126.GG6369@dastard> <515082C3.2000006@xxxxxxxxxxxxxx> <515361B5.8050603@xxxxxxxxxxxxxxxxx> <5155F2B2.1010308@xxxxxxxxxxxxxx> <20130331012231.GJ6369@dastard> <515C3BF3.60601@xxxxxxxxxxxxxx> <51684382.50008@xxxxxxxxxxxxxx> <5168AC0B.5010100@xxxxxxxxxxxxxxxxx>|
|User-agent:||Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:184.108.40.206) Gecko/20121215 Icedove/3.0.11|
Stan,I understand that this will be an ongoing problem. It seems like all I could do at this point would be to ' manually defrag' my inodes the hard way by doing this 'copy' operation whenever things slow down. (Either that or go get my PHD in file systems and try to come up with a better inode management algorithm.) I will be keeping two copies of this data going forward anyways.
Are there any other suggestions you might have at this time - xfs or otherwise?
-Dave Dave Hall Binghamton University kdhall@xxxxxxxxxxxxxx 607-760-2328 (Cell) 607-777-4641 (Office) On 04/12/2013 08:51 PM, Stan Hoeppner wrote:
On 4/12/2013 12:25 PM, Dave Hall wrote:Stan, IDid this post get lost in the shuffle? Looking at it I think it could have been a bit unclear. What I need to do anyways is have a second, off-site copy of my backup data. So I'm going to be building a second array. In copying, in order to preserve the hard link structure of the source array I'd have to run a sequence of cp -al / rsync calls that would mimic what rsnapshot did to get me to where I am right now. (Note that I could also potentially use rsync --link-dest.) So the question is how would the target xfs file system fare as far as my inode fragmentation situation is concerned? I'm hoping that since the target would be a fresh file system, and since during the 'copy' phase I'd only be adding inodes, that the inode allocation would be more compact and orderly than what I have on the source array since. What do you think?The question isn't what it will look like initially, as your inodes shouldn't be sparsely allocated as with your current aged filesystem. The question is how quickly the problem will arise on the new filesystem as you free inodes. I don't have the answer to that question. There's no way to predict this that I know of.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22, Eric Sandeen|
|Next by Date:||ФКС и ФЗ-94, Комитет государственного заказа|
|Previous by Thread:||Re: xfs_fsr, sunit, and swidth, Stan Hoeppner|
|Next by Thread:||Re: xfs_fsr, sunit, and swidth, Stan Hoeppner|
|Indexes:||[Date] [Thread] [Top] [All Lists]|