| View previous topic :: View next topic |
| Author |
Message |
depontius
Advocate
Joined: 05 May 2004
Posts: 3522
|
 Posted: Mon Oct 19, 2020 3:39 pm Post subject: Installing new machine, can't mount f2fs |
 |
|
I'm installing a new machine, first time with an nvme SSD, so I'm using f2fs. It won't mount.
So at the moment I'm stuck. Any suggestions?
EDIT - Discarded, didn't edit. (yet)
| Code: | [root@sysrescue /mnt/gentoo]# mount -t f2fs /dev/nvme0n1p2 /mnt/gentoo
mount: /mnt/gentoo: mount(2) system call failed: Structure needs cleaning.
[root@sysrescue /mnt/gentoo]# fsck.f2fs -f /dev/nvme0n1p2
Info: Force to fix corruption
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 122880000 (60000 MB)
Info: MKFS version
"Linux version 5.4.71-1-lts (linux-lts@archlinux) (gcc version 10.2.0 (GCC)) #1 SMP Wed, 14 Oct 2020 16:39:16 +0000"
Info: FSCK version
from "Linux version 5.4.71-1-lts (linux-lts@archlinux) (gcc version 10.2.0 (GCC)) #1 SMP Wed, 14 Oct 2020 16:39:16 +0000"
to "Linux version 5.4.71-1-lts (linux-lts@archlinux) (gcc version 10.2.0 (GCC)) #1 SMP Wed, 14 Oct 2020 16:39:16 +0000"
Info: superblock features = 29f8 : extra_attr project_quota inode_checksum flexible_inline_xattr quota_ino inode_crtime sb_checksum compression
Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
Info: total FS sectors = 122880000 (60000 MB)
Info: CKPT version = 1531fc23
Info: Checked valid nat_bits in checkpoint
Info: checkpoint state = 381 : allow_nocrc trimmed nat_bits unmount
[FSCK] Unreachable nat entries [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0x0]
[FSCK] valid_block_count matching with CP [Ok..] [0xb]
[FSCK] valid_node_count matching with CP (de lookup) [Ok..] [0x4]
[FSCK] valid_node_count matching with CP (nat lookup) [Ok..] [0x4]
[FSCK] valid_inode_count matched with CP [Ok..] [0x4]
[FSCK] free segment_count matched with CP [Ok..] [0x7474]
[FSCK] next block offset is free [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs [Ok..]
Done: 0.227678 secs
[root@sysrescue /mnt/gentoo]# mount -t f2fs /dev/nvme0n1p2 /mnt/gentoo
mount: /mnt/gentoo: mount(2) system call failed: Structure needs cleaning.
[root@sysrescue /mnt/gentoo]# |
_________________
.sigs waste space and bandwidth |
|
| Back to top |
|
 |
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2852
|
| Posted: Mon Oct 19, 2020 3:45 pm Post subject: |
|
|
| I know it doesn't help your current issue but I'd recommend to reconsider F2FS for a SSD, F2FS is better suited for dumb flash storage (like say, a USB thumbdrive), not a modern nvme SSD that knows very well how to handle itself. |
|
| Back to top |
|
|
depontius
Advocate
Joined: 05 May 2004
Posts: 3522
|
| Posted: Mon Oct 19, 2020 4:03 pm Post subject: |
|
|
| Ionen wrote: | | I know it doesn't help your current issue but I'd recommend to reconsider F2FS for a SSD, F2FS is better suited for dumb flash storage (like say, a USB thumbdrive), not a modern nvme SSD that knows very well how to handle itself. |
Heck, there is no data on the drive. I can redo filesystem creation.
I just found the Gentoo NVMe wiki, which says nothing about filesystem recommendations. Then I went over to the Gentoo SSD wiki, and as an example it uses ext4, and goes on to talk about stride and stripe, to align to the SSD blocks. However I can't find anything about those factors in the documentation. I've also read elsewhere that with SSD it's a good idea to disable the ext4 journal in order to minimize writes.
Just in case someone else knows the stride and stripe factors or can tell me where to find them or what good guesses are, this is a Western Digital Blue 500G NVMe.
_________________
.sigs waste space and bandwidth |
|
| Back to top |
|
|
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6148
Location: Dallas area
|
| Posted: Mon Oct 19, 2020 4:11 pm Post subject: |
|
|
I didn't do anything to add my nvme (samsung) just used gparted with the default start/spacing.
As far as minimizing writes (with modern nvme's, thats really not needed) so feel free to use whatever fs you want, I use btrfs on mine, no problem.
Ext4 should be perfectly fine, with or without writes to disk.
_________________
UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
| Back to top |
|
|
Goverp
Advocate
Joined: 07 Mar 2007
Posts: 2179
|
| Posted: Tue Oct 20, 2020 12:43 pm Post subject: Re: Installing new machine, can't mount f2fs |
|
|
| depontius wrote: | I'm installing a new machine, first time with an nvme SSD, so I'm using f2fs. It won't mount.
So at the moment I'm stuck. Any suggestions?
EDIT - Discarded, didn't edit. (yet)
| Code: | [root@sysrescue /mnt/gentoo]# mount -t f2fs /dev/nvme0n1p2 /mnt/gentoo
mount: /mnt/gentoo: mount(2) system call failed: Structure needs cleaning.
... |
|
I don't know if it's relevant, but IIUC you're mounting your SSD at /mnt/gentoo while you're actually in /mnt/gentoo. Not sure if that works.
Sadly I've no other useful suggestions: I built my machine in exactly this way, with an F2FS root on an nvme, and it all worked. From what I've read, F2FS was designed (by Samsung) with SSDs in mind not particularly USB thumb drives. I get the usual issue with F2FS of demanding an fsck when the kernel version changes, which is IMHO a sensible file system should avoid, but now I've an appropriate script in my initramfs, I've had no problems, and certainly not the one you're seeing. This isn't your problem; the kernel versions and mkfs version are all consistent.
Your listing's checkpoint state differs from mine: I assume the number is some bit mask corresponding to the words following, though I can find no documentation about it. My successful fsck.f2fs says: | Code: | | Info: checkpoint state = 41 : crc unmount |
compare yours: | Code: | | Info: checkpoint state = 381 : allow_nocrc trimmed nat_bits unmount |
This may indicate something odd about your filesystem's status.
_________________
Greybeard |
|
| Back to top |
|
|
depontius
Advocate
Joined: 05 May 2004
Posts: 3522
|
| Posted: Tue Oct 20, 2020 1:20 pm Post subject: |
|
|
I ended up going with ext4 and no journal. The emerge world started with 777 packages yesterday afternoon, and there are 64 to go. Then of course I have to build a kernel and configuration stuff.
_________________
.sigs waste space and bandwidth |
|
| Back to top |
|
|
szatox
Advocate
Joined: 27 Aug 2013
Posts: 3432
|
| Posted: Tue Oct 20, 2020 6:54 pm Post subject: |
|
|
| Quote: | | I ended up going with ext4 and no journal. |
Power never runs out in your area?
Do you have enough IOPS there to satisfy your use case? You're unlikely to kill your SSD unless you're intentional with it. |
|
| Back to top |
|
|
depontius
Advocate
Joined: 05 May 2004
Posts: 3522
|
| Posted: Tue Oct 20, 2020 9:33 pm Post subject: |
|
|
| szatox wrote: | | Quote: | | I ended up going with ext4 and no journal. |
Power never runs out in your area?
Do you have enough IOPS there to satisfy your use case? You're unlikely to kill your SSD unless you're intentional with it. |
Whole-house UPS - a Tesla PowerWall.
_________________
.sigs waste space and bandwidth |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22656
|
| Posted: Wed Oct 21, 2020 2:58 am Post subject: Re: Installing new machine, can't mount f2fs |
|
|
| Goverp wrote: | | I don't know if it's relevant, but IIUC you're mounting your SSD at /mnt/gentoo while you're actually in /mnt/gentoo. Not sure if that works. |
It works, but the results are a bit confusing to people not familiar with mount rules. The current working directory is unchanged, and continues to be the old value of /mnt/gentoo. Meanwhile, a path walk into gentoo from /mnt will find the new mount. Thus, ls -l . $PWD will list two different directories. |
|
| Back to top |
|
|
|
Installing Gentoo
