| 1 |
On 03/31/2017 09:50 AM, tuxic@××××××.de wrote: |
| 2 |
> On 03/31 10:59, Nils Freydank wrote: |
| 3 |
>> [...] |
| 4 |
>>> The fsck.*'s are built in |
| 5 |
>> |
| 6 |
>> I agree: |
| 7 |
>> |
| 8 |
>> % bb |
| 9 |
>> ~ $ which fsck |
| 10 |
>> ~ $ fsck -v |
| 11 |
>> fsck (busybox 1.26.2, 2017-03-12 11:38:12 CET) |
| 12 |
>> |
| 13 |
>> |
| 14 |
>> -- |
| 15 |
>> GPG fingerprint: '00EF D31F 1B60 D5DB ADB8 31C1 C0EC E696 0E54 475B' |
| 16 |
>> Nils Freydank |
| 17 |
> |
| 18 |
> Ok, if its builtin then back to the initial question: |
| 19 |
> How does this implementation compares to the "official" stuff of |
| 20 |
> e2fsprogs and friends? |
| 21 |
> Any experiences with that ? |
| 22 |
> |
| 23 |
> Thanks a lot for any help in advance! |
| 24 |
> |
| 25 |
> Cheers |
| 26 |
> Meino |
| 27 |
> |
| 28 |
> |
| 29 |
|
| 30 |
e2fsprogs provides two different executables that matter for this |
| 31 |
discussion, fsck and e2fsck. There are also symlinks from fsck.ext2, |
| 32 |
fsck.ext3, and fsck.ext4 pointing to e2fsck, so I will use these name |
| 33 |
interchangeably. The busybox executable provides an implementation of |
| 34 |
fsck, but not one for e2fsck. The fsck executable reads your /etc/fstab |
| 35 |
file and calls the appropriate fsck.${FSTYPE} for each filesystem you |
| 36 |
wish to check (and, in the case of busybox's implementation, tries to |
| 37 |
call fsck.auto for filesystems not listed in /etc/fstab if you don't |
| 38 |
otherwise tell it which filesystem type the filesystem is). Busybox |
| 39 |
itself does not have any implementation of fsck.ext4, just the fsck |
| 40 |
wrapper itself. You need an fsck.ext4 implementation to actually check |
| 41 |
your filesystem, which can be provided by e2fsprogs's e2fsck. If you do |
| 42 |
not have a fsck.ext4 executable, then busybox fsck will be unable to |
| 43 |
actually do any check on your ext4 filesystem. |
| 44 |
|
| 45 |
If your filesystem is not ext4, but instead something else, like vfat, |
| 46 |
then you would need the appropriate fsck.vfat (or whatever), and could |
| 47 |
use ether implementation of fsck to call it, but you would still need |
| 48 |
fsck.vfat. The only exception to this is if you are using the minix |
| 49 |
filesystem (which you probably aren't), in which case there is a |
| 50 |
fsck.minix applet that can be compiled into busybox, but is not included |
| 51 |
by default. |
| 52 |
|
| 53 |
-- |
| 54 |
Jonathan Callen |
Archives