Problem with mkfs and a LUKS XFS partition

English Install/Boot/Login
1

I’m running OpenSuSE 13.1 on an ASUS i7 x86_64 laptop.

I want to reformat one of my encrypted XFS partitions with the additional option -n version=ci but the YaST partitioner does not allow me to enter miscellaneous XFS options while formatting a partition.

When I format this partition with the YaST partitioner it takes about 10 seconds; when I try (as root) to use the mkfs command it never completes. I have tried various different ways:


mkfs.xfs -v -n version=ci /dev/mapper/cr_ata-ST9640320AS_5WX0XWKJ-part8
mkfs.xfs -v -f -n version=ci /dev/mapper/cr_ata-ST9640320AS_5WX0XWKJ-part8
mkfs -V -t xfs -f -n version=ci /dev/mapper/cr_ata-ST9640320AS_5WX0XWKJ-part8

None of these completes.** ^C** does not terminate them.** atop** shows no I/O activity on the drive. Only these two messages appear when mkfs starts:


mkfs from util-linux 2.23.2
mkfs.xfs -f -n version=ci /dev/mapper/cr_ata-ST9640320AS_5WX0XWKJ-part8

Can anyone explain what I’m doing wrong? I have pored over both the mkfs and mkfs.xfs man pages and if the answer is there, I can’t see it.

2

On 2014-01-13 20:56, jlturriff wrote:

> Code:
> --------------------
>
> mkfs.xfs -v -n version=ci /dev/mapper/cr_ata-ST9640320AS_5WX0XWKJ-part8
> mkfs.xfs -v -f -n version=ci /dev/mapper/cr_ata-ST9640320AS_5WX0XWKJ-part8
> mkfs -V -t xfs -f -n version=ci /dev/mapper/cr_ata-ST9640320AS_5WX0XWKJ-part8
>
> --------------------

I do not see that version in the man page. I only see 1 and 2.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

3

1 and 2 are from info mkfs.xfs; 3 is from info mkfs. In any case, I have not been able to find a method that works.

4

On 2014-01-14 03:36, jlturriff wrote:

>> I do not see that version in the man page. I only see 1 and 2.
>
> 1 and 2 are from info mkfs.xfs; 3 is from info mkfs. In any case, I
> have not been able to find a method that works.

Ok, I found it. Not in “info mkfs”, that one says nothing.


>        -n naming_options
>               These options specify the version and size parameters for the naming (directory) area of  the  filesys-
>               tem. The valid naming_options are:
>
>                    size=value | log=value
>                           The  block  size is specified either as a value in bytes with size=, or as a base two loga-
>                           rithm value with log=.  The block size must be a power of 2 and cannot  be  less  than  the
>                           filesystem  block  size.  The default size value for version 2 directories is 4096 bytes (4
>                           KiB), unless the filesystem block size is larger than 4096, in which case the default value
>                           is  the filesystem block size.  For version 1 directories the block size is the same as the
>                           filesystem block size.
>
>                    version=value
>                           The naming (directory) version value can be either 2 or 'ci', defaulting to 2  if  unspeci-
>                           fied.  With version 2 directories, the directory block size can be any power of 2 size from
>                           the filesystem block size up to 65536.
>
>                           The version=ci option enables ASCII only case-insensitive filename  lookup  and  version  2
>                           directories.  Filenames  are  case-preserving, that is, the names are stored in directories
>                           using the case they were created with.
>
>                           Note: Version 1 directories are not supported.

You really want “ASCII only case-insensitive filenames”? That’s
incompatible with Linux filesystems, I do not know if that is feasible.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

5

How would I know unless I try it? It may not be usable, but only trying it will tell.

6

On 2014-01-14 04:56, jlturriff wrote:

> How would I know unless I try it? It may not be usable, but only trying
> it will tell.

Well, because Linux filesystem is by design case sensitive. You simply
can not store Linux files in there. I see no use case for such a feature.

You can ask on the opensuse mail list instead, or create a Bugzilla
because the process locks. There is also a support XFS mail list or
forum or something (I used it years ago, I don’t remember the details)
where you could ask about it.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

7

Funny, I was just looking at the XFS mailing list archive, and there certainly are posts from users who are using the feature on Linux; so in fact it does work on Linux. (Why would it not? It’s just a case translation feature during lookups.)

I presume, then, that my command syntax is not the issue; that was the main thing I was wondering about.

8

On 2014-01-15 09:06, jlturriff wrote:

> I presume, then, that my command syntax is not the issue; that was the
> main thing I was wondering about.

You have to ask more people. The syntax seems correct to me.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

9

Finally, an answer to my original question.