Bug 234499

Summary: [NEW PORT] sysutils/ezfsck: Utility script to fsck all ufs/ext2/ext3/ext4 partitions
Product: Ports & Packages Reporter: bourne.identity <bourne.identity>
Component: Individual Port(s)Assignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: Open ---    
Severity: Affects Only Me CC: bourne.identity, pi
Priority: --- Keywords: feature, needs-qa
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
shar archive for ezfsck
none
Correct shar archive for ezfsck
none
shar archive for ezfsck with minor update
none
shar archive for ezfsck with major update none

Description bourne.identity@hotmail.com 2018-12-30 01:55:43 UTC
Created attachment 200612 [details]
shar archive for ezfsck

A utility script that automatically carries out fsck on all UFS/EXT2/EXT3/EXT4
hard-disk partitions listed in /etc/fstab.
Comment 1 bourne.identity@hotmail.com 2018-12-30 02:03:03 UTC
Created attachment 200613 [details]
Correct shar archive for ezfsck

Wrong shar was previously uploaded. Sorry !

MJ
Comment 2 bourne.identity@hotmail.com 2018-12-30 10:02:45 UTC
Kubilay,

Tx for taking this up.

I am not particularly sure whether the following 2 settings in the Makefile are right (considering dependency on fsck.ext2:sysutils/e2fsprogs):

NO_BUILD=   yes
NO_ARCH=    yes

Can you please confirm whether these settings are valid ?

Tx again.
MJ
Comment 3 bourne.identity@hotmail.com 2018-12-30 15:45:20 UTC
Created attachment 200623 [details]
shar archive for ezfsck with minor update

Spotted a missing feature - let user skip fsck during interactive operation.
This feature has now been bundled in, and I am quite sure ezfsck is final now.
Comment 4 Kurt Jaeger freebsd_committer 2019-01-12 18:52:11 UTC
HDPREFIX in the script implicitly assumes ada-only disks ? What about nvd0 or da0 like drives ?
Comment 5 bourne.identity@hotmail.com 2019-01-12 20:10:34 UTC
Hi Kurt/others,

Glad to hear from you, as well as to reassure you that I personally find ezfsck extremely useful after a bad shutdown.

The 'ada-only' hook is deliberate. Removable disks almost never need to fsck'ed after a bad shutdown, but each hard-disk partition should ideally by fsck'ed. So I do not cater to da0. As for nvd0, I have no idea what that is (removable or fixed hard-disk ?).

Kindly advise whether you consider the scheme advisable, compared to greater flexibility for looping in non-ada disks too.


Thanks.
Manish Jain
Comment 6 Kurt Jaeger freebsd_committer 2019-01-12 20:12:12 UTC
da0 are scsi or raid drives
nvd0 are nvme drives

so they are not always removable
Comment 7 bourne.identity@hotmail.com 2019-01-12 20:25:15 UTC
Hi Kurt/others,

Thanks for reverting so quickly.

I think I shall change the scheme to optionally pull in other disks too via options. And I glad to learn about nvme drives.

Please hold on for a day or two, and I will upload a new shar.


Regards,
Manish Jain
Comment 8 bourne.identity@hotmail.com 2019-01-16 19:58:49 UTC
Created attachment 201194 [details]
shar archive for ezfsck with major update

ezfsck now iterates over /dev/[ada*/da*/nvd*] - ada* is mandatory; other types can be specified on the command-line invocation.

I do not have any nvme disk, and therefore request committer to check --nvme at his/her end.


Thanks.
Manish Jain