Tiny Core Base > Raspberry Pi

Disk partition - 3 partitions

<< < (3/4) > >>

TimJ:
Another partitioning question.

I write piCore to a sdcard on my PC using Ubuntu 18.04, and whilst there use gparted to increase the partition size and add any extras partitions, but if I then try to use fsck on the Pi i just get this.


--- Code: ---tc@box:~$ sudo fsck /mnt/mmcblk0
fsck (busybox 1.28.4)
fsck: fsck.auto: No such file or directory
tc@box:~$
--- End code ---

Not a major problem as I just put the card back in the PC. But wondering what was the cause?

Tim

curaga:
That is the device, not the partition.

Paul_123:
Bela,

Stable might not be the right choice of words, but I've had a number of cases when testing f2fs, where a file system was "successfully" created, but the drive would not mount......   the exact problem the OP had.   It seemed to be dependent on the size of the partition created.

Once a partition was mounted, it did seem to work okay, but my unofficial benchmark tests showed times varied by about 90 seconds on a 7min test  (I ran tests 5 times)   ext4 was much more consistent on the same test. 

Paul

bmarkus:
Hi Paul

thanks. By default I'm using ext4. In piCore10 base btrfs kernel module is also included. It is stable and reliable. btrfs partition mounts slower than ext4fs but performance is good.

Paul_123:
I did btrfs testing too. 

-Mounts slow as you noted
-Modules are extremely large.
-btrfs-progs packages has extra dependencies.
-Smallest partition with separate data and metadata regions is ~115MB.  (Doesn't make it a good candidate for the tce partition)
-Average performance was similar to ext4.   Some test runs were much faster and some runs were slower.
-The self healing is interesting.....but not sure that is of much value in a read-only file system.

xfs was not a clear winner either.

Navigation

[0] Message Index

[#] Next page

[*] Previous page