Fresh install FreeBSD-10.0-CURRENT-i386-20130108-r245175-release.iso
in virtualbox 4.2 (Host -- FreeBSD-9 amd64).
After install run in headless mode, login by ssh.
mount -u -o async /
rm -r /usr/port
Got trap http://zxy.spb.ru/trap.png
___
freebsd-curr
Should I be getting trim with ZFS on an mps device?
Disks are SATA ssd (830s), only "unsupported" is being reported.
Do I need to set the cam "da" delete method to something (unmap?), or is
ZFS trim only supported on ahci sata controllers?
vfs.zfs.trim_disable: 0
vfs.zfs.trim_txg_limit: 64
kstat.
On Fri, Jan 18, 2013 at 11:56:27AM -0500, Ryan Stone wrote:
> I have been experiencing occasional deadlocks on FreeBSD 8.2 systems using
> the ULE scheduler. The root cause in every case has been that ULE's
> TDQ_LOCK for cpu 0 is owned by a thread that is not running. I have been
> investigating
Borrowed USB stick today and did same excersize as below (# zpool create tank
raidz da5{d,e,f}) with exactly same outcome.
On 19.01.2013, at 23:26, Alexander Nedotsukov wrote:
> Hi All,
>
> Just a note that after catch up with -current my zfs pool kissed good bye.
> I'll omit details about it
TB --- 2013-01-20 12:25:42 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-01-20 12:25:42 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
On Sun, Jan 20, 2013 at 5:29 AM, Konstantin Belousov wrote:
> Both atrtc and hpet register the interrupt handler as the filter.
> The filters call loop enters critical section around handlers, see
> kern_intr.c:intr_event_handle(). At least on HEAD it is so, and I see
> the same code in the 8.
>
- Original Message -
From: "matt"
To:
Sent: Sunday, January 20, 2013 9:39 AM
Subject: ZFS Trim on mps?
Should I be getting trim with ZFS on an mps device?
Disks are SATA ssd (830s), only "unsupported" is being reported.
Do I need to set the cam "da" delete method to something (unmap
On Fri, 18 Jan 2013, Larry Rosenman wrote:
Never mind, it's in VirtualBox itself. The line is at ~~line 8020 in the
same file. I've patched it and am recompiling
VirtualBox.
If I don't see the panic for a few days, I'll submit a PR.
I've submitted the PR, because for nehalem class or better
Today something unusual happened on one of my machines:
kernel: (ada0:ahcich0:0:0:0): lost device
kernel: (aprobe1:ahcich0:0:15:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00
kernel: (aprobe1:ahcich0:0:15:0): CAM status: Command timeout
kernel: (aprobe1:ahcich0:0:15:0): Error 5, Retries exhaust
On Thu, Jan 17, 2013 at 2:15 PM, Alfred Perlstein wrote:
> On 1/17/13 1:22 PM, John Baldwin wrote:
>>
>> Running 'ps axH' on a current system results in a lot of kthreads with not
>> very useful names (unless you add -c):
>>
>>PID TT STAT TIME COMMAND
>> 0 ?? DLs1:09.52 [kern
TB --- 2013-01-20 22:23:20 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-01-20 22:23:20 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
11 matches
Mail list logo