You are not logged in.

#1 2013-06-05 16:29:45

STUART
Member
From: Seattle, WA
Registered: 2010-08-19
Posts: 38
Website

Can't mount a new F2FS partition

[stuart@sturling ~]$ sudo mkfs.f2fs /dev/sdc2

	F2FS-tools: mkfs.f2fs Ver: 1.1.0 (2012-11-29)

Info: sector size = 512
Info: total sectors = 122681344 (in 512bytes)
Info: zone aligned segment0 blkaddr: 256
Info: format successful
[stuart@sturling ~]$ sudo modprobe f2fs
[stuart@sturling ~]$ sudo mount -t f2fs /dev/sdc2 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sdc2,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
[stuart@sturling ~]$ dmesg | tail
[432658.009671] F2FS-fs (sdc2): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[432658.009678] F2FS-fs (sdc2): Can't find a valid F2FS filesystem in first superblock
[432658.011732] F2FS-fs (sdc2): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[432658.011739] F2FS-fs (sdc2): Can't find a valid F2FS filesystem in second superblock
[stuart@sturling ~]$ lsblk -ft
NAME    FSTYPE  LABEL         UUID                                 MOUNTPOINT            NAME    ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE  RA WSAME
sdc                                                                                      sdc             0    512      0     512     512    1 cfq       128 128    0B
├─sdc1  vfat    SAVFAT        ECE9-161D                                                  ├─sdc1          0    512      0     512     512    1 cfq       128 128    0B
├─sdc2                                                                                   ├─sdc2          0    512      0     512     512    1 cfq       128 128    0B
└─sdc3  ext4    saboot        ccc5c2b8-2cee-4e77-83bc-79e31a6ac15b                       └─sdc3          0    512      0     512     512    1 cfq       128 128    0B

What is happening? Why?

Last edited by STUART (2013-06-05 16:30:18)

Offline

#2 2013-06-05 16:37:27

karol
Archivist
Registered: 2009-05-06
Posts: 25,433

Re: Can't mount a new F2FS partition

Is it related to https://bugs.archlinux.org/task/35353 ?
This is the only thing I can find in Arch BT, but you can google further.

Offline

#3 2013-06-05 16:45:52

STUART
Member
From: Seattle, WA
Registered: 2010-08-19
Posts: 38
Website

Re: Can't mount a new F2FS partition

It doesn't seem that way. `blkid /dev/sdc2` yields no output.

Last edited by STUART (2013-06-06 03:23:58)

Offline

#4 2013-06-05 17:41:42

HalosGhost
Member
From: Twin Cities, MN
Registered: 2012-06-22
Posts: 1,486
Website

Re: Can't mount a new F2FS partition

STUART wrote:

It doesn't seem that way. `blkid /dev/sdc1` yields no output.

You made sure to run that as root or with sudo, right? `blkid` doesn't post any output for unprivileged users.

All the best,

-HG


"All errors are ᴘᴇʙᴋᴀᴄ errors—It's just a matter of narrowing down which keyboard and chair." -Trilby
\ldots

Offline

#5 2013-06-06 03:25:41

STUART
Member
From: Seattle, WA
Registered: 2010-08-19
Posts: 38
Website

Re: Can't mount a new F2FS partition

HalosGhost wrote:

You made sure to run that as root or with sudo, right? `blkid` doesn't post any output for unprivileged users.

I get the same results with or without sudo for /dev/sdc1, /dev/sdc2, and /dev/sdc3: no output for 2 and what you see above for 1 and 3.

Offline

#6 2013-06-26 17:30:42

STUART
Member
From: Seattle, WA
Registered: 2010-08-19
Posts: 38
Website

Re: Can't mount a new F2FS partition

Signs point to this being an issue with the system's built-in SD card reader (for some reason it is incapable of writing/reading F2FS). Not sure if this is a known issue or if there's somewhere to report a bug.

Last edited by STUART (2013-06-26 17:37:12)

Offline

#7 2013-06-26 18:53:48

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,097
Website

Re: Can't mount a new F2FS partition

STUART wrote:

Signs point to this being an issue with the system's built-in SD card reader (for some reason it is incapable of writing/reading F2FS). Not sure if this is a known issue or if there's somewhere to report a bug.

I call bullshit. Your card reader could not care less what's on the media it's reading from. It serves up blocks of data to the kernel which is capable of understanding f2fs via the FS driver.

I'm far more inclined to believe that mkfs.f2fs is buggy.

Offline

#8 2013-06-28 17:55:42

STUART
Member
From: Seattle, WA
Registered: 2010-08-19
Posts: 38
Website

Re: Can't mount a new F2FS partition

falconindy wrote:
STUART wrote:

Signs point to this being an issue with the system's built-in SD card reader (for some reason it is incapable of writing/reading F2FS). Not sure if this is a known issue or if there's somewhere to report a bug.

I call bullshit. Your card reader could not care less what's on the media it's reading from. It serves up blocks of data to the kernel which is capable of understanding f2fs via the FS driver.

I'm far more inclined to believe that mkfs.f2fs is buggy.

I'm just calling 'em as I see 'em. I created a f2fs partition on the USB reader where it read successfully, then moved the card to the built-in reader, where I got the magic number error described above.

Offline

#9 2013-06-28 22:17:04

STUART
Member
From: Seattle, WA
Registered: 2010-08-19
Posts: 38
Website

Re: Can't mount a new F2FS partition

It's been suggested to me via email that this could be a reader capacity issue, which could be possible (as the working partitions are in the first 4 gigabytes and the f2fs partition is being created in the last 60 gigabytes).

Offline

#10 2013-07-04 11:45:27

STUART
Member
From: Seattle, WA
Registered: 2010-08-19
Posts: 38
Website

Re: Can't mount a new F2FS partition

It looks like this might be a problem with the card (one that manifests differently on different hardware). After giving up and reformatting to ext4, this is the output from dmesg | tail from 3 failed mount attempts:

[ 1639.472802] EXT4-fs (sdb2): ext4_check_descriptors: Checksum for group 0 failed (36153!=0)
[ 1639.472813] EXT4-fs (sdb2): group descriptors corrupted!
[ 1857.448540] EXT4-fs (sdb2): ext4_check_descriptors: Checksum for group 0 failed (13388!=0)
[ 1857.448550] EXT4-fs (sdb2): group descriptors corrupted!
[ 2485.605093] EXT4-fs (sdb2): ext4_check_descriptors: Checksum for group 0 failed (12136!=0)
[ 2485.605099] EXT4-fs (sdb2): group descriptors corrupted!

I tried remaking the FS between attempts 2 and 3 - no dice.

For what it's worth, the output from flashbench:

align 17179869184	pre 2.64ms	on 3.64ms	post 2.62ms	diff 1.01ms
align 8589934592	pre 2.55ms	on 3.54ms	post 2.82ms	diff 853µs
align 4294967296	pre 2.64ms	on 3.94ms	post 2.99ms	diff 1.13ms
align 2147483648	pre 2.56ms	on 3.52ms	post 3.05ms	diff 711µs
align 1073741824	pre 2.52ms	on 3.53ms	post 2.43ms	diff 1.06ms
align 536870912	pre 2.53ms	on 3.56ms	post 2.77ms	diff 913µs
align 268435456	pre 2.69ms	on 3.39ms	post 2.43ms	diff 835µs
align 134217728	pre 2.46ms	on 3.2ms	post 2.42ms	diff 760µs
align 67108864	pre 2.48ms	on 3.2ms	post 2.44ms	diff 738µs
align 33554432	pre 2.49ms	on 3.2ms	post 2.42ms	diff 748µs
align 16777216	pre 2.63ms	on 2.66ms	post 2.64ms	diff 31.2µs
align 8388608	pre 2.41ms	on 2.43ms	post 2.49ms	diff -21069n
align 4194304	pre 2.46ms	on 2.48ms	post 2.46ms	diff 23.9µs
align 2097152	pre 2.43ms	on 2.45ms	post 2.47ms	diff 2.87µs
align 1048576	pre 2.36ms	on 2.28ms	post 2.29ms	diff -52518n
align 524288	pre 2.35ms	on 2.35ms	post 2.34ms	diff 7.51µs
align 262144	pre 2.32ms	on 2.36ms	post 2.36ms	diff 23.7µs
align 131072	pre 2.39ms	on 2.36ms	post 2.32ms	diff 5.38µs
align 65536	pre 2.33ms	on 2.37ms	post 2.38ms	diff 14.6µs
align 32768	pre 2.36ms	on 2.33ms	post 2.33ms	diff -15694n
-O
4MiB    1.18M/s 
2MiB    1.66M/s 
1MiB    1.49M/s 
512KiB  2.01M/s 
256KiB  1.88M/s 
128KiB  2.11M/s 
64KiB   2.03M/s 
32KiB   1.94M/s 
16KiB   1.71M/s 

(I'd have this saved locally but writes to my normal system card have gotten really slow due to heat or something)

TLDR / EDIT FOR POSTERITY: This was a "64 GB" card I bought on eBay for ~$10. Unsurprisingly, it was a faulty card.

Last edited by STUART (2014-04-15 20:29:54)

Offline

Board footer

Powered by FluxBB