On Mon, Jun 19, 2000, Adrian Chadd wrote:
> On Mon, Jun 19, 2000, David O'Brien wrote:
> > On Mon, Jun 19, 2000 at 01:42:33PM +0200, Adrian Chadd wrote:
> > > I've ported the NetBSD fsck wrapper to compile and run under FreeBSD.
> >
> > Can you summerize what this does, or does better than what we do today?
>
> The idea is the same as mount and its helpers - adding new fsck types
> doesn't require modifying the startup scripts or fsck. Think of a system
> where you have an FFS fs, an LFS fs, and perhaps an IFS fs. Each one
> requires a seperate fsck, but it would be stupid to have fsck_* -p in
> the rc scripts.
>
> Eventually FreeBSD systems will have more than just FFS based filesystems
> running the system, and users will want to fsck them just like a FFS
> filesystem.
Watching my machine boot, the parallel nature of this fsck is now
confusing the output, eg:
Automatic reboot in progress...
** /dev/ad0s1a
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
de0: enabling 10baseT port
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
1506 files, 57594 used, 10837 free (285 frags, 1319 blocks, 0.4% fragmentation)
** /dev/amrd0a
** /dev/ad0s1f
** Last Mounted on /cache
** Phase 1 - Check Blocks and Sizes
** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
** Phase 2 - Check Pathnames
98429 files, 1812888 used, 2499978 free (181498 frags, 289810 blocks, 4.2%
fragmentation)
..
Would people object to fsck printing out either the mountpoint or the
devname (where appropriate) prepending each line of fsck_ffs ?
Adrian
--
Adrian Chadd Build a man a fire, and he's warm for the
<[EMAIL PROTECTED]> rest of the evening. Set a man on fire and
he's warm for the rest of his life.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
