| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: free inodes remaining in 1tb |
| From: | Carlos Maiolino <cmaiolino@xxxxxxxxxx> |
| Date: | Fri, 27 Sep 2013 09:47:13 -0300 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20130927081844.GA14996@xxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Mail-followup-to: | xfs@xxxxxxxxxxx |
| References: | <44qehaxod8.ln2@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20130927010847.GW26872@dastard> <20130927081844.GA14996@xxxxxxxxxxxxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
Hi, > On 2013-09-26, Carlos Maiolino <cmaiolino@xxxxxxxxxx> wrote: > > bear in mind though that are some applications that can't read 64bit > > inodes. > > I know that NFS has some issues (documented in the XFS FAQ). Do you > know offhand of any other examples? > My apologies, I'm not a heavy user of applications that handle file's inodes. What I can tell you is that any application that might need to handle file's inodes would be worth to check if they can handle 64bit inodes, for example, some backup applications use to handle inodes for some reason (read it as 'I have no idea how these backup apps works' :), and I've seen some reports about problems with backup applications for this reason some time ago, but can't really point you out anything specific. -- Carlos |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs hardware RAID alignment over linear lvm, Stewart Webb |
|---|---|
| Next by Date: | [PATCH] xfs: fix memory leak in xfs_dir2_node_removename, Mark Tinguely |
| Previous by Thread: | Re: free inodes remaining in 1tb, Stefan Ring |
| Next by Thread: | si el puede,vos tambien, auhtpn |
| Indexes: | [Date] [Thread] [Top] [All Lists] |