Hi!
I've noticed that ZFS on 8.1-STABLE still has problems with sendfile.
When accessing a file at first time the transfer speed is too low, but
on following attempts the transfer speed is normal.
How to repeat:
$ dd if=/dev/random of=/tmp/test bs=1m count=100
100+0 records in
100+0 records out
Thanks Artem,
I am mainly concerned about fixing this immediate problem first and then if
I
can provide more information for the developers so that they look into this
problem
I'd be happy to.
I'll try OpenSolaris live CD and see how it goes. Either way I'll report
back here.
Cheers,
Rumen Telbi
Are you interested in what's wrong or in how to fix it?
If fixing is the priority, I'd boot from OpenSolaris live CD and would
try importing the array there. Just make sure you don't upgrade ZFS to
a version that is newer than the one FreeBSD supports.
Opensolaris may be able to fix the array. On
No ideas whatsoever?
On Tue, Oct 26, 2010 at 1:04 PM, Rumen Telbizov wrote:
> Hello everyone,
>
> After a few days of struggle with my degraded zpool on a backup server I
> decided to ask for
> help here or at least get some clues as to what might be wrong with it.
> Here's the current state of
Am 27.10.2010 um 22:51 schrieb S.N.Grigoriev:
> Hi list,
>
> I've got very low write speed using ZFS on a SATA disk.
> My HDD configuration is:
> ad4: 70911MB at ata2-master UDMA100 SATA 3Gb/s
> ad6: 78532MB at ata3-master UDMA100 SATA
> 1.5Gb/s
> ad8: 1430799MB at ata4-master UDMA100 SATA
>
Sean C. Farley-2 wrote:
>
> For me, the solution appeared to be setting the grace time to three
> seconds to avoid the slowdown of the drive: gracetime=3
> At least, the disc worked on subsequent burns this way. Jakub, you may
> try to see if this setting helps.
>
No, gracetime doesn't hel
Hi list,
I've got very low write speed using ZFS on a SATA disk.
My HDD configuration is:
ad4: 70911MB at ata2-master UDMA100 SATA 3Gb/s
ad6: 78532MB at ata3-master UDMA100 SATA
1.5Gb/s
ad8: 1430799MB at ata4-master UDMA100 SATA 3Gb/s
ad4 and ad6 are single-slice disks (UFS2 with soft updates)
> This is often caused by a combination of two things being enabled
> simultaneously: BIOS-level serial console redirection after POST, and
> FreeBSD's serial console support.
bingo!
thanks
randy
___
freebsd-stable@freebsd.org mailing list
http://lists
On Thu, Oct 28, 2010 at 04:47:00AM +0900, Randy Bush wrote:
> on the serial console, i am seeing twirlies doubled, as in
>
> //
>
> and the beastie is very tortured
>
>
> +-++¿Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä|Ä-Ä
>
on the serial console, i am seeing twirlies doubled, as in
//
and the beastie is very tortured
+-++¿Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä|Ä-Ä
||³
||³ ||³ ,,
On Tue, 26 Oct 2010 17:01:01 +0100 Pete French wrote:
PF> Actually, I just llooked I dmesg on the secondary - it is full
PF> of messages thus:
PF> Oct 26 15:44:59 serpentine-passive hastd[10394]: [serp0] (secondary)
Unable to receive request header: RPC version wrong.
PF> Oct 26 15:45:00 s
Jeremy Chadwick writes:
> $ uname -a
> FreeBSD icarus.home.lan 8.1-STABLE FreeBSD 8.1-STABLE #0: Sat Oct 16 07:10:54
> PDT 2010 r...@icarus.home.lan:/usr/obj/usr/src/sys/X7SBA_RELENG_8_amd64
> amd64
> $ sudo -i
> icarus# rm -fr /usr/obj/*
> rm: No match.
> icarus# cd /usr/src
icarus# make
On Wed, Oct 27, 2010 at 06:48:58AM -0700, Jeremy Chadwick wrote:
> On Wed, Oct 27, 2010 at 09:27:03AM -0400, John Baldwin wrote:
> > On Wednesday, October 27, 2010 3:44:02 am Jeremy Chadwick wrote:
> > > The below commit has broken the ability to build system boot blocks
> > > (including pxeldr) th
On Wed, Oct 27, 2010 at 09:27:03AM -0400, John Baldwin wrote:
> On Wednesday, October 27, 2010 3:44:02 am Jeremy Chadwick wrote:
> > The below commit has broken the ability to build system boot blocks
> > (including pxeldr) the "historic way"[1]:
> >
> > http://freshbsd.org/2010/10/17/20/10/00
> >
On Wednesday, October 27, 2010 3:44:02 am Jeremy Chadwick wrote:
> The below commit has broken the ability to build system boot blocks
> (including pxeldr) the "historic way"[1]:
>
> http://freshbsd.org/2010/10/17/20/10/00
>
> The breakage on RELENG_8 (dated as of a few minutes ago):
>
> ===
on 27/10/2010 12:17 Jeremy Chadwick said the following:
> On Wed, Oct 27, 2010 at 10:08:17AM +0200, Pawel Jakub Dawidek wrote:
>> The proper way is to:
>>
>> # cd /usr/src
>> # make buildenv
>> # cd sys/boot
>> # make clean && make && make install
>
> Thanks for the tip -- the
On Wed, Oct 27, 2010 at 10:08:17AM +0200, Pawel Jakub Dawidek wrote:
> On Wed, Oct 27, 2010 at 12:44:02AM -0700, Jeremy Chadwick wrote:
> > The below commit has broken the ability to build system boot blocks
> > (including pxeldr) the "historic way"[1]:
> >
> > http://freshbsd.org/2010/10/17/20/10
On Wed, Oct 27, 2010 at 12:44:02AM -0700, Jeremy Chadwick wrote:
> The below commit has broken the ability to build system boot blocks
> (including pxeldr) the "historic way"[1]:
>
> http://freshbsd.org/2010/10/17/20/10/00
>
> The breakage on RELENG_8 (dated as of a few minutes ago):
>
> ===
The below commit has broken the ability to build system boot blocks
(including pxeldr) the "historic way"[1]:
http://freshbsd.org/2010/10/17/20/10/00
The breakage on RELENG_8 (dated as of a few minutes ago):
# rm -fr /usr/obj/*
# cd /sys/boot
# make clean
19 matches
Mail list logo
