Linux chattr: [Errno 95] Operation not supported

[Lasse Kliemann]

Upon restoring, I get

Linux chattr: [Errno 95] Operation not supported:

loads of times, looks like for each of the files that is restored. This
happens when restoring to a ZFS volume (the backup was taken on
EXT4). Restoring to EXT4 is fine. So I guess it is harmless and just
something not supported on ZFS. But it would be great if this message
could be switched off for such cases since other error messages may get
lost in the clutter.

--
Kind Regards / MfG
Dr. Lasse Kliemann
Westring 269, 24116 Kiel, Germany
E-Mail: la...@lassekliemann.de
OpenPGP Key: 0x4296A3E08903D018
Phone: +49 162 66 88 468
Web: http://lassekliemann.de

Work Address:
Department of Mathematics
Kiel University
Ludewig-Meyn-Str. 4
24118 Kiel, Germany
Phone: +49 431 880 1155

[Rob Browning]

Lasse Kliemann <la...@lassekliemann.de> writes:

> Upon restoring, I get
>
> Linux chattr: [Errno 95] Operation not supported:
>
> loads of times, looks like for each of the files that is restored. This
> happens when restoring to a ZFS volume (the backup was taken on
> EXT4). Restoring to EXT4 is fine. So I guess it is harmless and just
> something not supported on ZFS. But it would be great if this message
> could be switched off for such cases since other error messages may get
> lost in the clutter.

Yes, I think that may be expected right now, and completely agree with
respect to eventually having better accommodations for cases like this.

Though at the moment, I'm not at all sure what the solution should look
like. You could imagine "warn once" semantics like we have for other
things, but that's not necessarily sufficient, and could/should you try
to make it per-filesystem (if the restore straddles more than one)?

Another option that I suspect might be preferable, at least as an
initial option, is a way to manually suppress various warnings that you
expect, and also don't want contributing contributing to the exit
status, i.e. (hand waving):

bup restore ... --ignore-error no-chattr ...

(While working on some other things I also realized that resources
permitting, we may eventually want to make some changes to our metadata
types to better track where the stat (etc.) information came from,
and/or to not (only) rely on binary compatibility for some of the
fields like the mode.)

Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

[Lasse Kliemann]

Rob Browning <r...@defaultvalue.org> writes:

>> Upon restoring, I get
>>
>> Linux chattr: [Errno 95] Operation not supported:

> Though at the moment, I'm not at all sure what the solution should look
> like. You could imagine "warn once" semantics like we have for other
> things, but that's not necessarily sufficient, and could/should you try
> to make it per-filesystem (if the restore straddles more than one)?

For the time being, it would probably be enough to have some reasonable
default of this kind (warn once per filesystem), and using -v or -vv or
some debug option will make all the messages come out as they do now.

A message could be:

Warning: Filesystem at ... does not support operation ... . This
operation will be skipped for all files on this filesystem.