ACL Corruption Bug

NASbox

Guru
Joined
May 8, 2012
Messages
650
I noticed this bug is still open as of 11.1U7 - https://redmine.ixsystems.com/issues/53199

This prompted me to do a quick check since I am using zfs send/recv to make my backups.

Here is what I got from a quick check, and IIUC everything is fine. Am I correct?

Does anyone know when/why the corruption occurs?

Is there a quck way to check for it, or do I have to navigate into the snapshot directory of every dataset and list it?


Code:
#>zfs list -t all -r BACKUP03/TANK/library
NAME                                                      USED  AVAIL  REFER  MOUNTPOINT
BACKUP03/TANK/library                                    4.34T  1.65T  4.34T  /BACKUP03/TANK/library
BACKUP03/TANK/library@__BKP03_7XXXXXXC__20180423_011627  2.06M      -  4.29T  -
BACKUP03/TANK/library@__BKP03_7XXXXXXC__20190124_044551   280K      -  4.33T  -
BACKUP03/TANK/library@__BKP03_7XXXXXXC__20190325_144917      0      -  4.34T  -


Code:
#>getfacl __BKP03_7XXXXXXC__20190325_144917
# file: __BKP03_7XXXXXXC__20190325_144917
# owner: library
# group: library
            owner@:rwxpDdaARWcCos:fd-----:allow
            group@:rwxpDdaARWcCos:fd-----:allow
         everyone@:r-x---a-R-c---:fd-----:allow
       
#>getfacl __BKP03_7XXXXXXC__20190124_044551
# file: __BKP03_7XXXXXXC__20190124_044551
# owner: library
# group: library
            owner@:rwxpDdaARWcCos:fd-----:allow
            group@:rwxpDdaARWcCos:fd-----:allow
         everyone@:r-x---a-R-c---:fd-----:allow

#>getfacl __BKP03_7XXXXXXC__20180423_011627
# file: __BKP03_7XXXXXXC__20180423_011627
# owner: library
# group: library
            owner@:rwxpDdaARWcCos:fd-----:allow
            group@:rwxpDdaARWcCos:fd-----:allow
         everyone@:r-x---a-R-c---:fd-----:allow


Code:
#>getfacl __BKP03_7XXXXXXC__20190325_144917
# file: __BKP03_7XXXXXXC__20190325_144917
# owner: library
# group: library
            owner@:rwxpDdaARWcCos:fd-----:allow
            group@:rwxpDdaARWcCos:fd-----:allow
         everyone@:r-x---a-R-c---:fd-----:allow

#>getfacl __BKP03_7XXXXXXC__20190124_044551
# file: __BKP03_7XXXXXXC__20190124_044551
# owner: library
# group: library
            owner@:rwxpDdaARWcCos:fd-----:allow
            group@:rwxpDdaARWcCos:fd-----:allow
         everyone@:r-x---a-R-c---:fd-----:allow

#>getfacl __BKP03_7XXXXXXC__20180423_011627
# file: __BKP03_7XXXXXXC__20180423_011627
# owner: library
# group: library
            owner@:rwxpDdaARWcCos:fd-----:allow
            group@:rwxpDdaARWcCos:fd-----:allow
         everyone@:r-x---a-R-c---:fd-----:allow
 
D

dlavigne

Guest
Notes that the fix depends upon which train you are on (eg it was fixed for 11.2-U2 on #57888). This was one of those "heisenbugs" that was hard to reproduce but had been occasionally seen in the wild.
 

NASbox

Guru
Joined
May 8, 2012
Messages
650
Notes that the fix depends upon which train you are on (eg it was fixed for 11.2-U2 on #57888). This was one of those "heisenbugs" that was hard to reproduce but had been occasionally seen in the wild.

Since I am on 11.1U7, I assume that I am still affected by the bug. Are there been any common conditions? Any quick way of testing or do I need to go directory by directory like I did in the OP?
 
D

dlavigne

Guest
Everything we found that could possibly reproduce it is in the notes on that ticket.
 
Top