I need help restoring my /usr partition!
Lowell Gilbert
freebsd-questions-local at be-well.ilk.org
Wed Nov 5 05:39:07 PST 2003
Mark <admin at asarian-host.net> writes:
> I need some urgent help! Trying to restore my /usr partition (FreeBSD 4.7R),
> I get the following errors:
>
> % restore -N -rf ./usr.back
> expected next file 1125, got 7
> expected next file 1125, got 8
> expected next file 1125, got 529
> expected next file 1125, got 530
> expected next file 6995, got 6872
> expected next file 6995, got 6873
> expected next file 8502, got 8483
> expected next file 8502, got 8484
> expected next file 8828, got 8736
> expected next file 8828, got 8737
> expected next file 22844, got 9619
Sounds like problems with the backup,
not the disk you're restoring to.
> Etc. This is the result of the fsck:
>
> % fsck /usr
> ** /dev/ad0s1g (NO WRITE)
> ** Last Mounted on /usr
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> UNREF FILE I=7 OWNER=nobody MODE=100644
> SIZE=1744 MTIME=Nov 3 14:33 2003
> CLEAR? no
>
> UNREF FILE I=8 OWNER=nobody MODE=100644
> SIZE=6952 MTIME=Nov 4 10:52 2003
> CLEAR? no
>
> UNREF FILE I=529 OWNER=root MODE=100660
> SIZE=0 MTIME=Nov 3 00:08 2003
> CLEAR? no
>
> UNREF FILE I=530 OWNER=root MODE=100660
> SIZE=1521 MTIME=Nov 3 09:13 2003
> CLEAR? no
>
>
> I have no idea what these file are, or how to get rid of them. Somebody,
> please help!
Looks like you're doing your fsck while the filesystem is mounted
read-write. Don't do that. Unmount it first (single-user mode is
good for this), and *then* fsck it. You probably won't find any
problems at that time, though -- the unreferenced file handles may
just be normal open handles that will be cleaned up when the
filesystem is umounted and flushed to disk.
More information about the freebsd-questions
mailing list