========
dump/restore doesn't support the ea_inode (will exclude in the future)
generic/319
===========
Looks like some kind of ENOSPC error when inheriting the acl
(this may be a journal credits issue?):
@@ -9,13 +9,5 @@
default:group::rwx
default:other::---
-# file: SCRATCH_MNT/testdir/testsubdir
-# owner: root
-# group: root
-user::rwx
-group::rwx
-other::---
-default:user::rwx
-default:group::rwx
-default:other::---
-
+mkdir: cannot create directory '/xt-vdc/testdir/testsubdir': No space left on device
+getfacl: /xt-vdc/testdir/testsubdir: No such file or directory
generic/388
===========
Shutting down a file system while it is busy can lead to the file
system getting corrupted. This failure exists on other configs, and
is an known issue that needs to be looked into.
generic/397
===========
Another ENOSPC issue, this time with the ext4 encryption feature
enabled. I suspect again that it's a journal credits issue because
the file system size is not constrained and the test isn't initially
trying to fill the free space to test for ENOSPC allocation bugs.
@@ -1,7 +1,10 @@
QA output created by 397
+ln: failed to create symbolic link '/xt-vdc/edir/symlink3': No space left on device
+Only in /xt-vdc/ref_dir: symlink3
+Only in /xt-vdc/ref_dir: symlink3
stat: cannot stat 'SCRATCH_MNT/edir/empty': No such file or directory
stat: cannot stat 'SCRATCH_MNT/edir/symlink': No such file or directory
-8
+7
1
Required key not available
SCRATCH_MNT/edir/newfile: Required key not available
generic/422
===========
This one is weird because we're not trying to test for xattrs and I
don't belive xattrs are being created at all. So I'm not sure where
the file size change is coming from:
@@ -27,7 +27,7 @@
Space used by file foo3:
128K SCRATCH_MNT/foo3
Space used by file foo4:
-64K SCRATCH_MNT/foo4
+68K SCRATCH_MNT/foo4
After writeback
@@ -38,4 +38,4 @@
Space used by file foo3:
128K SCRATCH_MNT/foo3
Space used by file foo4:
-64K SCRATCH_MNT/foo4
+68K SCRATCH_MNT/foo4