| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | xfsdump and chattr +d : undocumented but really useful behaviour |
| From: | "Gerard Neil" <xyzzy@xxxxxxxxxxxxx> |
| Date: | Mon, 3 Apr 2006 13:55:10 +1000 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=WI0sQvjO2xD51X/+okK8AaTg0KBXKs+uGOjQg6pIXrdryRmxs4A0UVoK+hcEDJxgTxIaidA7M0z6dnOLKCS4LXEIfERdYK4o0/cYSkwbvX7cJ3D786FEHjWvxyVCCHw7tD3C39rqU0ozQaBnQoAR1d1frNXkrFNHQZGb2MbWXAI= |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
I've been running a gentoo linux server (currently 2.6.15) using xfs and xfsdump for a couple of years now. I've just discovered that if the the no-dump (d) attribute is set on a directory (using chattr +d), then any new directories/files created in that directory automatically acquire the attribute too. This is *really* useful when used in conjunction with xfsdump -e, because it means I can easily exclude entire subtrees from dumps. If this is really how the no-dump attribute is supposed to behave on xfs, then I suggest documenting this in the xfsdump man page. The current "excluding individual files" section is confusing with respect to chattr +d, and certainly doesn't mention this useful behaviour. I can't find it documented anywhere else, either... Regards, Gerard |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Next by Date: | Re: xfsdump and chattr +d : undocumented but really useful behaviour, Bill Kendall |
|---|---|
| Next by Thread: | Re: xfsdump and chattr +d : undocumented but really useful behaviour, Bill Kendall |
| Indexes: | [Date] [Thread] [Top] [All Lists] |