-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/10/2011 04:21 AM, Arne Jansen wrote:
> Now that I've got a working prototype of subvolume quota, I'd like
> to get some feedback on the on-disk structure and the commands I
> intend to use.
I think I've noticed a bug so far, and have one comment
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The --rootdir switch was not documented in the man page
Signed-off-by: Phillip Susi
- ---
man/mkfs.btrfs.8.in |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/man/mkfs.btrfs.8.in b/man/mkfs.btrfs.8.in
index 542e6cf..25e817
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There were extra spaces around some of the arguments in the man
page for mkfs.
Signed-off-by: Phillip Susi
- ---
man/mkfs.btrfs.8.in | 19 ++-
1 files changed, 10 insertions(+), 9 deletions(-)
diff --git a/man/mkfs.btrfs.8.in b/ma
Okay, I built the version you sent me. I am guessing that this has the
newest btrfs code in it even though it is labeled 3.1.0? Is that
because it has not been merged? Relevant commands and a stack trace
below. Still says something about a null pointer.
root@berna:~# uname -a
Linux berna 3.1.0+ #3
> My mistake, the same printks are printed when the encryption key is
> incorrect, I've seen that here.
> It looks like you have some ugly hardware errors.
> The kernel cannot read from the drive, so it cannot guess the file system on
> it.
> If the data is valuable, you could try to ddrescue the
