User talk:YHNdnzj

From ArchWiki
Latest comment: 4 April by YHNdnzj in topic Change wiki btrfs

Change wiki btrfs

Hi YHNdnzj,

i have seen, you changed the btrfs wiki back.

I don't understand the reason.

The current changed back version is not working.

I added to the warning article the link, where is solved the issue i had when i tried to create swap on btrfs. it is the the way how i changed it to wiki. Have you read it?

Maybe this way is not ideal (i don't know currently better), but it is working, current is not.

i understand the archwiki is like wiki for users, not professionals, so it should have full working solution, which current is not.

If you don't like my change, I'm ok with it, but in that case change the btrfs wiki yourself, so it will contain working solution. Otherwise i feel we can delete whole unworking part of swap on btrfs, so user will go it find on google and spend a lot of time like me. KSJ (talk) 12:09, 2 April 2024 (UTC)Reply[reply]

> The current changed back version is not working.
The current procedures *are* working. My guess is that you try to mount the nested subvol - there's no need. Nested subvols behave like normal dirs.
> i understand the archwiki is like wiki for users, not professionals, so it should have full working solution, which current is not.
No. If you follow the steps closely it would work.
-- YHNdnzj (talk) 12:15, 2 April 2024 (UTC)Reply[reply]
I will try it. In case it will work, i will move the tip at the end of the swap part of article, because it seems i'm not on confused one.
The step above the tip will make impossible to mount it.
Or how do you feel about remove the tip and make two complete possible ways?
in other articles are two ways too. E.g. for mysql and postgress. KSJ (talk) 12:39, 2 April 2024 (UTC)Reply[reply]
Also there's a key difference between Wiki and Guide: the former uses inter-page links extensively, and don't try to fit a "full working solution" into one page. Even if the current version doesn't work, please don't place random `mount` commands in. They simply don't belong to the section. -- YHNdnzj (talk) 12:18, 2 April 2024 (UTC)Reply[reply]
You mean the tip? It will not work. And just mount will not help. But i understand and rewrite it differentry. But there is still need to use /mnt i tried ./@swap and /@swap and @swap and it will always create nested subvolume which cannot be mount KSJ (talk) 12:50, 2 April 2024 (UTC)Reply[reply]
No. Please do not try to make this a guide. The tip has provided sufficient info/context if you want to try flat layout. -- YHNdnzj (talk) 13:02, 2 April 2024 (UTC)Reply[reply]
I cannot find a way how to check the size of the flat subvolume (if it is subvolume, which contains the swapfile and not root subvolume), so I have to believe it is correct. KSJ (talk) 11:12, 3 April 2024 (UTC)Reply[reply]
Your edit is still spurious. The existing example uses *nested* subvol layout, not flat.
A flat layout means to place any subvol directly under top-level subvol, i.e. what is suggested in tips and requires extra mounts. The nested layout means to place swap subvol under your @root subvol, such subvols do not need to be mounted.
-- YHNdnzj (talk) 11:38, 3 April 2024 (UTC)Reply[reply]
I understood how it works. But not the correct name for them. Is there some way how do find out if the directory is a directory or the nested layout btrfs subvolume? In filesystem they looks the same. KSJ (talk) 12:03, 3 April 2024 (UTC)Reply[reply]
Through the following command (and pay attention to the parent field):
# btrfs subvolume list -p /
If the parent subvol id is sth other than 5, it's a nested subvol. -- YHNdnzj (talk) 12:07, 3 April 2024 (UTC)Reply[reply]
I'll close the topic here. Your edit now looks good, and I hope I have answered all questions properly :) -- YHNdnzj (talk) 16:37, 4 April 2024 (UTC)Reply[reply]