Bug 38119 - No way to create XFS with `-n ftype=1` flag
Summary: No way to create XFS with `-n ftype=1` flag
Status: CLOSED WORKSFORME
Alias: None
Product: Branch p8
Classification: Distributions
Component: alterator-vm (show other bugs)
Version: не указана
Hardware: x86_64 Linux
: P5 major
Assignee: Andrey Cherepanov
QA Contact: qa-p8@altlinux.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-18 17:49 MSK by Svetlana
Modified: 2020-02-19 10:48 MSK (History)
0 users

See Also:


Attachments
vm-profile.scm draft (283 bytes, text/x-scheme)
2020-02-18 17:49 MSK, Svetlana
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Svetlana 2020-02-18 17:49:23 MSK
Created attachment 8620 [details]
vm-profile.scm draft

Hello guys. 

I have a necessity to create VM templates based on Alt Linux. And I encountered the following problem: there is no way to create XFS with `-n ftype=1` flag using `alterator-vm` package. 

I drafted attached .scm code as the vm-profile.scm and it works ok. But I can't use those templates for further docker installation, 'cause I catch «overlay2: the backing XFS filesystem is formatted without d_type support, which leads to incorrect behaviour.» error.

Maybe there is some way to pass params through the .scm profile but it's obscured for me. Official Alt wiki has no mention of such capabilities. 

--
best, Svetlana.
Comment 1 Svetlana 2020-02-18 18:02:16 MSK
I have to add that I'm using p9 version.
Comment 2 Sergey Bolshakov 2020-02-18 18:40:18 MSK
(In reply to Svetlana from comment #0)

> I have a necessity to create VM templates based on Alt Linux. And I
> encountered the following problem: there is no way to create XFS with `-n
> ftype=1` flag using `alterator-vm` package. 

alterator-vm uses mkfs.xfs internally, and ftype=1 is the default value
for it -- i believe there's no need to pass it explicitly.
are you sure you actually create new xfs filesystem ?

> I drafted attached .scm code as the vm-profile.scm and it works ok. But I
> can't use those templates for further docker installation, 'cause I catch
> «overlay2: the backing XFS filesystem is formatted without d_type support,
> which leads to incorrect behaviour.» error.

> Maybe there is some way to pass params through the .scm profile but it's
> obscured for me. Official Alt wiki has no mention of such capabilities. 

probably because they do not exist -- there's no way to pass such things down, sorry
Comment 3 Svetlana 2020-02-18 19:16:47 MSK
Hello, Sergey. 
I'm awfully sorry, I made a mistake. It's p8.

cat /proc/varsion:
>>Linux version 4.19.36-std-def-alt1 (builder@localhost.localdomain) 
>>(gcc version 8.3.1 20190311 (ALT Sisyphus 8.3.1-alt2) (GCC)) 
>>#1 SMP Mon Apr 22 19:38:57 UTC 2019

cat /etc/redhat-release:
>>ALT 8.2 Server

cat /etc/fstab:
>>proc		/proc			proc	nosuid,noexec,gid=proc		0 0
>>devpts	/dev/pts		devpts	nosuid,noexec,gid=tty,mode=620	0 0
>>tmpfs		/tmp			tmpfs	nosuid				0 0
>>UUID=333f6252-e5d9-4cdd-b729-dd325b85248e	/	xfs	relatime	1 1
>>UUID=eca01acf-d994-4ed7-b2a7-4ca8fb7502a7	/boot	xfs	nodev,nosuid,noexec,relatime 1 2
>>UUID=b49bfce1-23ff-42e5-a173-7b91b627f781	swap	swap	defaults	0 0

I do use exactly the same vm-profile.scm file as above.
Maybe any log file will aid you?
Comment 4 Svetlana 2020-02-18 19:18:35 MSK
fs_info /
>meta-data=/dev/sda5              isize=256    agcount=4, agsize=3080128 blks
>         =                       sectsz=512   attr=2
>data     =                       bsize=4096   blocks=12320512, imaxpct=25
>         =                       sunit=0      swidth=0 blks
>naming   =version 2              bsize=4096   ascii-ci=0
>log      =internal               bsize=4096   blocks=1280, version=2
>         =                       sectsz=512   sunit=0 blks, lazy-count=1
>realtime =none                   extsz=4096   blocks=0, rtextents=0
Comment 5 Svetlana 2020-02-18 19:49:10 MSK
I figured out that p8 installation iso use xfsprogs v3.1.11 (Nov 2015)
And the latest is 5.4. 

Maybe back in 2015, there was no `-n ftype=1` option, and Alt dev team has to bump package version? I actually don't know. Please correct me if I'm wrong.
Comment 6 Andrey Cherepanov 2020-02-19 10:48:09 MSK
Possible WONTFIX in unsupported branch.