--- Mike Wolman [EMAIL PROTECTED] wrote:
It could also be used for asynchronous mirrors over slow links, if the log
device was always written to first then the write latency for long distant
links could be removed. Im not sure if it would be possible to achieve
this using just a modified
--- O. Hartmann [EMAIL PROTECTED] wrote:
Before digging into this problem deeper with benchmarks, could anyone
explain why FreeBSD reaches this 33 MB/s limit (sounds like UDMA 33
defaults, but on both boxes nForce4 and ICH5 controller are recognized
and show up with SATA300 or SATA150
--- Matthew Seaman [EMAIL PROTECTED] wrote:
Marc G. Fournier wrote:
So, again, if I'm reading through things correctly, I'll have to do
something like:
gstripe st1 da1 da2
gstripe st2 da3 da4
gmirror drive st1 st2
newfs drive
That's the wrong way round, I think. If you lose
--- Brent Hostetler [EMAIL PROTECTED] wrote:
mode 04277 inum=12258433 fs=/usr/local/smbshares
panic: ffs_vallov: dup alloc
I say, did u try a fsck on that file system?
It looks more like an file system related problem.
I would try an
fsck -n ...
first (just in case there is a configuration
