Of course ZFS doesn't need fsck. Until it fails.
Did you personally try ZFS ?
of course.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
I think it's likely that it is a 64-bit installation.
Not sure about that. How could the amd64 OS be installed
and run on a i386 machine?
it cannot.
___
freebsd-questions@freebsd.org mailing list
On 07/08/2012 22:09, Wojciech Puchar wrote:
Of course ZFS doesn't need fsck. Until it fails.
It doesn't need fsck for the normal case of filesystem corruption due to
system crashes: in that case, you stand to lose maybe the last one or
two IO transactions that hadn't made it onto the disk yet,
Needing fsck because the drive is failing and not able to store and
retrieve data reliably any more is a whole different thing.
or bad data stored because of non-disk errors.
least will discover that this is happening due to the built-in
checksumming and avoid many instances of silent
Free Gold Combat - Calling Arcade Gamers to Shooting Mayhem
Gold Combat HD, Arcade Shooting Gold Rush
Hi, There
We would like to introduce our newly launched game on app store Gold Combat (
blackfriar wrote:
Hi everybody!
I'm wondering if it's possible to run in a clear fashion an NFS server
within a jail on FreeBSD 9.0.
I'm having some issues that make me think this is not supposed to work.
I've googled it but I couldn't find much especially on releases prior
5!!
A quick tip
Clear!
Thanks a lot.
On Wed, 2012-08-08 at 10:02 -0400, Fbsd8 wrote:
blackfriar wrote:
Hi everybody!
I'm wondering if it's possible to run in a clear fashion an NFS server
within a jail on FreeBSD 9.0.
I'm having some issues that make me think this is not supposed to work.
I've
On Wed, Aug 8, 2012 at 9:02 AM, Fbsd8 fb...@a1poweruser.com wrote:
Long answer is; NFS requires rpcbind to function. rpcbind is dependent on
a network stack. Jails do not have their own network stack, they use the
hosts network stack.
Dealing with this has been SOP practice in jails since
On Wed, 08 Aug 2012 11:55:51 -0500, Adam Vande More
amvandem...@gmail.com wrote:
There are a number of people who have reached the
opposite decision concerning VIMAGE/VNET enabled jails. They are much
easier to work with and provide nice capabilities.
I tried it on 9.0-RELEASE and was
Adam Vande More wrote:
On Wed, Aug 8, 2012 at 9:02 AM, Fbsd8 fb...@a1poweruser.com wrote:
Long answer is; NFS requires rpcbind to function. rpcbind is dependent on
a network stack. Jails do not have their own network stack, they use the
hosts network stack.
Dealing with this has been SOP
I am installing 8.3-RELEASE on an old 900mhz pentium laptop ... it's an
i686 CPU.
By default, GENERIC has HAMMER as the cpu, and that isn't working. So
I tried both:
you've got into wrong directory
/usr/src/sys/i386/conf is right
/usr/src/sys/amd64/conf is wrong, unless you have 64-bit
Greetings
FYI:
On or about August 1 I upgraded emacs to V. 24.x and when running it,
I found this error in a terminal:
GLib-WARNING **: In call to g_spawn_sync(), exit status of a child
process was requested but SIGCHLD action was set to SIG_IGN and ECHILD
was received by waitpid(), so
i installed the power PC version of free BSD and put it on my mac i book g3
i was in the insulation process when i couldn't get it to work because of a
few errors and i decided to turn it off and restart when i turned it back
on it only booted to a blank white screen it has nothing on it and
On 08/09/2012 06:22, Andy Recker wrote:
i installed the power PC version of free BSD and put it on my mac i book g3
i was in the insulation process when i couldn't get it to work because of a
few errors and i decided to turn it off and restart when i turned it back
on it only booted to a blank
== Jeff Tipton wrote on Thu 9.Aug'12 at 8:36:12 +0300 ==
On 08/09/2012 06:22, Andy Recker wrote:
i installed the power PC version of free BSD and put it on my mac i book g3
i was in the insulation process when i couldn't get it to work because of a
few errors and i decided to turn it off
15 matches
Mail list logo