| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: xfsrestore -t and default location of housekeeping dir |
| From: | Iustin Pop <iusty@xxxxxxxxx> |
| Date: | Fri, 18 Jul 2014 21:07:30 +0200 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20140717090550.GB27425@xxxxxxxxxxxxx> |
| Mail-followup-to: | xfs@xxxxxxxxxxx |
| References: | <20140714071935.GB29541@xxxxxxxxxxxxxxxxx> <20140717090550.GB27425@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.23 (2014-03-12) |
On Thu, Jul 17, 2014 at 02:05:50AM -0700, Christoph Hellwig wrote: > On Mon, Jul 14, 2014 at 09:19:35AM +0200, Iustin Pop wrote: > > Hi, > > > > While testing a just-made dump with via 'xfsrestore -t', I learned that > > the default housekeepingdir path is still under the original filesystem. > > My xfsrestore therefore failed, since that filesystem was read-only. > > > > Since '-t' should denote a pure no-op operation, with no changes, would > > it make more sense to default the housekeeping location to a temporary > > location if it is used? > > It seems to me like -t shouldn't recreate the files in the housekeeping > directory at all. I did take a brief look at the code and is a huge > mess that seems to recreate files unconditionally, so I don't really > have a good solution for this yet. Understood. Thanks! iustin |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Show off your wealth on your wrist , Xegtrqy |
|---|---|
| Next by Date: | Re: Error setting extent size on a directory, Iustin Pop |
| Previous by Thread: | Re: xfsrestore -t and default location of housekeeping dir, Christoph Hellwig |
| Next by Thread: | Re: xfs: two deadlock problems occur when kswapd writebacks XFS pages., Masayoshi Mizuma |
| Indexes: | [Date] [Thread] [Top] [All Lists] |