View previous topic :: View next topic |
Author |
Message |
Hund Apprentice
Joined: 18 Jul 2016 Posts: 218 Location: Sweden
|
Posted: Tue Dec 15, 2020 11:46 am Post subject: |
|
|
I use Alpine Linux on my Raspberry Pi. It runs from the memory and only writes to the SD-card when you tell it to save the changes.
If you don't use the SD-card you shouldn't be able to break it. :) _________________ Collect memories, not things. |
|
Back to top |
|
|
ShorTie Tux's lil' helper
Joined: 12 Feb 2006 Posts: 101
|
Posted: Tue Dec 15, 2020 12:14 pm Post subject: |
|
|
Just some food for thought
The pi foundation uses the ^huge_file option when they format.
So, like for me, it's a
Code: | echo y | mkfs.ext4 -O ^huge_file -L Gentoo $rootpart && sync |
|
|
Back to top |
|
|
gtwrek Tux's lil' helper
Joined: 10 Mar 2017 Posts: 110 Location: San Jose, CA
|
Posted: Wed Dec 16, 2020 12:53 am Post subject: |
|
|
FWIW, changing my root filesystem on the PI SD card to ext4 (all default options) seems to have solved things for me.
Previously, when my root was f2fs, I had a failure rate of 2/3 (units were my backup operation).
Changing to a new SD Card with ext4, and I've now run 18 iterations of my backup, without problems. Not scientifically rigorous, but that's good enough for me.
I don't know if there's (1) a problem with f2fs, or (2) if there's something wrong with f2fs on the PI, or (3) if there's something wrong with f2fs with a PI using SD cards. But it's not reliable for me and I won't be deploying any with this configuration. |
|
Back to top |
|
|
Goverp Advocate
Joined: 07 Mar 2007 Posts: 2179
|
Posted: Wed Dec 16, 2020 10:20 am Post subject: |
|
|
Worth reporting as an f2fs bug? _________________ Greybeard |
|
Back to top |
|
|
gtwrek Tux's lil' helper
Joined: 10 Mar 2017 Posts: 110 Location: San Jose, CA
|
Posted: Wed Dec 16, 2020 7:37 pm Post subject: |
|
|
Quote: | Worth reporting as an f2fs bug? |
I might try to. I'm not a software developer, and I've never filed any bugs against any free-software project. (Although I use such tools quite extensively within my organization, so I'm familiar with them).
I don't think the problem is in gentoo sys-f2/f2fs-tools, so filing a bug there doesn't seem correct. The counter argument would be to start small locally there and then push upstream.
From my read, it's f2fs itself - which goes right up to the kernel right? I don't even know where to start with filing a bug report there. Plus I don't have all that much confidence that my analysis is right, and I've not done something stupid on my end... Quite likely, the latter is the root cause - I'm one of those folks that knows just enough to get myself in trouble. |
|
Back to top |
|
|
Goverp Advocate
Joined: 07 Mar 2007 Posts: 2179
|
Posted: Thu Dec 17, 2020 10:13 am Post subject: |
|
|
The way to report kernel bugs is to start with the /usr/src/linux/MAINTAINERS file. It contains a description at the top, embedded within which it tells you the "B:" entries list the place to report bugs (though the file is mostly concerned with how to send patches). For F2FS, the MAINTAINERS entry is
Code: | F2FS FILE SYSTEM
M: Jaegeuk Kim <jaegeuk@kernel.org>
M: Chao Yu <yuchao0@huawei.com>
L: linux-f2fs-devel@lists.sourceforge.net
S: Maintained
W: https://f2fs.wiki.kernel.org/
T: git git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git
F: Documentation/ABI/testing/sysfs-fs-f2fs
F: Documentation/filesystems/f2fs.rst
F: fs/f2fs/
F: include/linux/f2fs_fs.h
F: include/trace/events/f2fs.h | (Sadly, the wiki is moribund.)
As there's no "B:" entry, I'd guess the default kernel bugzilla https://bugzilla.kernel.org/ is the place to report it, possibly with a post to the mailing list (the "L:" entry above, mailto:linux-f2fs-devel@lists.sourceforge.net) as a prompt (my experience with an AMDGPU bug was that its kernel developers don't look at bugzilla until prompted.) _________________ Greybeard |
|
Back to top |
|
|
Spargeltarzan Guru
Joined: 23 Jul 2017 Posts: 325
|
Posted: Wed Feb 03, 2021 9:56 am Post subject: |
|
|
Hi,
I have just burned two microSD cards SanDisk Extreme Pro 64gb just by extracting the stage3 to it and performing an emerge --sync in a qemu chroot.
I used the sd card in my notebook with an adapter. The first one came with a badly produced adapter, its write-protection switch was very loose and I was afraid I ruined the card because the switch was neither on or off while using it.
However, I also used f2fs on the cards. I wonder if that can be really the root cause since my cards didn't even touch the RPi but died in the chroot locally.
Once I have read a post from Neddy that modern high-performance cards might be less reliable than weaker classes, but once we have found a card reliable it will be a very long time. I wasn't aware of it and just ordered a fast card since I also want the RPi to be fast believing it will be also reliable.
What is your advice or opinion, should I order a weaker card, or similar but different brand, the same one or just trying to format next time ext4? _________________ ___________________
Regards
Spargeltarzan
Notebook: Lenovo YOGA 900-13ISK: Gentoo stable amd64, GNOME systemd, KVM/QEMU
Desktop-PC: Intel Core i7-4770K, 8GB Ram, AMD Radeon R9 280X, ZFS Storage, GNOME openrc, Dantrell, Xen |
|
Back to top |
|
|
gtwrek Tux's lil' helper
Joined: 10 Mar 2017 Posts: 110 Location: San Jose, CA
|
Posted: Wed Feb 03, 2021 4:23 pm Post subject: |
|
|
Since my Dec 15, post, I've converted 2 of my Pi's from f2fs filesystems on the SD card to ext4. Those systems have been 100% reliable since that time. I do gentoo world upgrade on those systems about 1/week.
I have one other Pi system that's still on f2fs - I've just not updated it because it's hard to get to physically. I'm not doing ANY updates on that system, as I'm quite convinced that doing so will kill the SD Card.
Personally, I'm quite convinced that the original configuration I deployed (with f2fs) is not reliable - although I'm not sure exactly what is the root cause. |
|
Back to top |
|
|
Spargeltarzan Guru
Joined: 23 Jul 2017 Posts: 325
|
Posted: Wed Feb 03, 2021 8:05 pm Post subject: |
|
|
Very strange since one would normally believe a filesystem made for sdcards should handle it even better.
Thanks for your response! _________________ ___________________
Regards
Spargeltarzan
Notebook: Lenovo YOGA 900-13ISK: Gentoo stable amd64, GNOME systemd, KVM/QEMU
Desktop-PC: Intel Core i7-4770K, 8GB Ram, AMD Radeon R9 280X, ZFS Storage, GNOME openrc, Dantrell, Xen |
|
Back to top |
|
|
benjamin3 n00b
Joined: 27 Feb 2024 Posts: 1
|
Posted: Tue Feb 27, 2024 1:38 pm Post subject: |
|
|
Hi Everyone,
I have seen a similar problem on other arm hardware and I am wondering if it is caused by this issue:
Quote: |
From: Avri Altman <avri.altman@wdc.com>
commit 07d2872bf4c864eb83d034263c155746a2fb7a3b upstream.
Some SD-cards from Sandisk that are SDA-6.0 compliant reports they supports
discard, while they actually don't. This might cause mk2fs to fail while
trying to format the card and revert it to a read-only mode.
To fix this problem, let's add a card quirk (MMC_QUIRK_BROKEN_SD_DISCARD)
to indicate that we shall fall-back to use the legacy erase command
instead.
|
https://lore.kernel.org/all/20221027165056.934451689@linuxfoundation.org/
I initially thought that it only happened with F2FS, but then I had it happen when I was reformatting an SD (mkfs.ext4). This lead me to search a bit wider and that's when I found the above patch. |
|
Back to top |
|
|
szatox Advocate
Joined: 27 Aug 2013 Posts: 3426
|
Posted: Tue Feb 27, 2024 3:10 pm Post subject: |
|
|
Since this topic popped up, I just wanted to say my rpi4 has been running happily for like 2 years by now.
Using f2fs on a relatively bulky, full-metal body pendrive - a deliberate choice hoping for better cooling than plastic body or fingernail-size would offer.
Granted, it runs under a very low load, but still no data corruption so far. _________________ Make Computing Fun Again |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|