Re: nodump on Linux

[Arian Kuschki <arian.kuschki@googlemail.com>]

The behaviour on my machine is the same as on Davids, i.e. it does not
work as expected.

Linux t420s 3.1.1-1-ARCH #1 SMP PREEMPT Fri Nov 11 22:28:29 CET 2011
x86_64 Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz GenuineIntel GNU/Linux

/dev/sda4 on /home type ext4 (rw,noatime,discard,user_xattr,commit=60)

David, have you found the reason for this behaviour?


On Thu, 29 Sep 2011 20:52:32 +0800 (WST), David Adam <zanchey@ucc.gu.uwa.edu.au> wrote:
> Just wondering if you'd had any further thoughts on this?
> 
> Thanks
> 
> David
> 
> On Sun, 18 Sep 2011, David Adam wrote:
> > On Sat, 17 Sep 2011, Colin Percival wrote:
> > 
> > > Hi David,
> > > 
> > > On 09/17/11 20:50, David Adam wrote:
> > > > I'm using tarsnap 1.0.30 on Ubuntu 11.04 and I'm a bit confused about when
> > > > the nodump flag is honoured.
> > > 
> > > It should be honoured whenever you use the --nodump option.  Something weird
> > > is going on here.
> > > 
> > > > Am I approaching this the wrong way?
> > > 
> > > No, you're quite right that what you're seeing doesn't make sense.
> > > 
> > > Is everything on the same filesystem?  What type of filesystem?  If you run
> > > tarsnap with the -w option, does it prompt on these directories?  Does tar
> > > work properly?  (Which version of tar did you try?)
> > 
> > Yep, this is all on the same filesystem, type ext4 
> > (rw,errors=remount-ro,commit=0).
> > 
> > Tarsnap does prompt with the -w option for the same pattern of directories 
> > as above.
> > 
> > GNU tar 1.25 on Ubuntu doesn't know or care about the dump flag/attribute.
> > 
> > > I'll probably have more questions later. ;-)
> > 
> > Thanks for your help!
> > 
> > David Adam
> > zanchey@ucc.gu.uwa.edu.au
> > 
> 
> Cheers,
> 
> David Adam
> zanchey@ucc.gu.uwa.edu.au
> Ask Me About Our SLA!