From owner-freebsd-questi...@freebsd.org Sat Jul 21 09:40:20 2012
Date: Sat, 21 Jul 2012 16:38:02 +0200
From: Leslie Jensen les...@eskk.nu
To: freebsd-questions@freebsd.org
Subject: Power failure during portsnap fetch update
My file system /usr/ports/net go damaged
I've done fsck -F in
I've done fsck -F in single user mode but there are warnings about not being
able to fix this.
without the messages from fsck i cannot help you.
there are rare cases when mess gets written to inodes that fsck will not
corrent it and you have to do it yourself. most often - using clri(8).
On Sat, 21 Jul 2012 16:38:02 +0200, Leslie Jensen wrote:
My file system /usr/ports/net go damaged
I've done fsck -F in single user mode but there are warnings about not
being able to fix this.
First of all, you should give fsck a second try. Check the
damaged partition per fsck -y
2012-07-21 16:44, Wojciech Puchar skrev:
I've done fsck -F in single user mode but there are warnings about not
being able to fix this.
without the messages from fsck i cannot help you.
there are rare cases when mess gets written to inodes that fsck will not
corrent it and you have to do
how about fsck_ffs -y / in single user mode?
seems like no clri is needed.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
On Sat, 21 Jul 2012 16:56:28 +0200, Leslie Jensen wrote:
Here are the errors:
root@bsd01~:fsck -F /dev/ad4s3f
** /dev/ad4s3f (NO WRITE)
In that case, fsck won't correct any errors. Good for checking,
bad for repairing!
Make sure the partition isn't mounted (e.
2012-07-21 16:59, Wojciech Puchar skrev:
how about fsck_ffs -y / in single user mode?
seems like no clri is needed.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org
It fixed the problem :-)
you may risk putting
fsck_y_enable=YES
in your rc.conf
i put background_fsck=NO in
2012-07-21 17:33, Wojciech Puchar skrev:
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org
It fixed the problem :-)
you may risk putting
fsck_y_enable=YES
in
