On 03/31/2017 09:50 AM, tu...@posteo.de wrote:
On 03/31 10:59, Nils Freydank wrote:
[...]
The fsck.*'s are built in
I agree:
% bb
~ $ which fsck
~ $ fsck -v
fsck (busybox 1.26.2, 2017-03-12 11:38:12 CET)
--
GPG fingerprint: '00EF D31F 1B60 D5DB ADB8 31C1 C0EC E696 0E54 475B'
Nils Freydank
Ok, if its builtin then back to the initial question:
How does this implementation compares to the "official" stuff of
e2fsprogs and friends?
Any experiences with that ?
Thanks a lot for any help in advance!
Cheers
Meino
e2fsprogs provides two different executables that matter for this
discussion, fsck and e2fsck. There are also symlinks from fsck.ext2,
fsck.ext3, and fsck.ext4 pointing to e2fsck, so I will use these name
interchangeably. The busybox executable provides an implementation of
fsck, but not one for e2fsck. The fsck executable reads your /etc/fstab
file and calls the appropriate fsck.${FSTYPE} for each filesystem you
wish to check (and, in the case of busybox's implementation, tries to
call fsck.auto for filesystems not listed in /etc/fstab if you don't
otherwise tell it which filesystem type the filesystem is). Busybox
itself does not have any implementation of fsck.ext4, just the fsck
wrapper itself. You need an fsck.ext4 implementation to actually check
your filesystem, which can be provided by e2fsprogs's e2fsck. If you do
not have a fsck.ext4 executable, then busybox fsck will be unable to
actually do any check on your ext4 filesystem.
If your filesystem is not ext4, but instead something else, like vfat,
then you would need the appropriate fsck.vfat (or whatever), and could
use ether implementation of fsck to call it, but you would still need
fsck.vfat. The only exception to this is if you are using the minix
filesystem (which you probably aren't), in which case there is a
fsck.minix applet that can be compiled into busybox, but is not included
by default.
--
Jonathan Callen
