On Thu, Dec 29, 2011 at 03:02:14PM -0800, David Thiel wrote:
> =
> Machine 1, with journal:
> =
>
> Script started on Thu Dec 29 11:26:29 2011
> fsck /
> ** /dev/ada0.eli
Correction - machine 1 had an unclean shutdown. Will get
On Wed, Dec 28, 2011 at 12:57:31AM -0700, Scott Long wrote:
> So, there's an assumption with SUJ+fsck that SU is keeping the filesystem
> consistent. Maybe that's a bad assumption, and I'm not trying to discredit
> your report. But the intention with SUJ is to eliminate the need for
> anything
On Tue, Dec 27, 2011 at 11:54:20PM -0700, Scott Long wrote:
> The first run of fsck, using the journal, gives results that I would
> expect. The second run seems to imply that the fixes made on the
> first run didn't actually get written to disk. This is definitely an
> oddity. I see that you
On Tue, Dec 27, 2011 at 02:48:22PM -0800, Xin Li wrote:
> >> - use journalled fsck; - use normal fsck to check if the
> >> journalled fsck did the right thing.
Ok, here is the log of fsck with and without journal.
http://redundancy.redundancy.org/fscklog3
That was done the very next boot, after
On Tue, Dec 27, 2011 at 02:29:03PM -0800, Xin LI wrote:
> I'm not sure if your experiments are right here, the second log shows
> you're running it read-only, which is likely caused by running it on
> live file system.
Yes, this most recent instance is me running it on a live FS, because
I'm us
I've had multiple machines now (9.0-RC3, amd64, i386 and earlier
9-CURRENT on ppc) running SU+J that have had unexplained panics and
crashes start happening relating to disk I/O. When I end up running a
full fsck, it keeps turning out that the disk is dirty and corrupted,
but no mechanism is in
On Sun, Feb 09, 2003 at 07:42:42PM +0100, Coercitas Temet'Nosce wrote:
> Hello all,
>
> I was just wondering something regarding IPFilter and new FreeBSD 5.0
>
> First, I was looking for IPF related functions in new Kernel building,
> didn't found them anywhere.maybe I did something wrong but not
A couple things regarding this new wireless driver - the
wepkey option to ifconfig no longer seems to work; I get a
"SIOCS80211: Invalid argument". Secondly and more importantly,
even when the wepkey is set via wicontrol, I can't seem to get
any connectivity at all anymore.
ifconfig wi0:
flags
