On Sat, 8 Jun 2013, Glen Barber wrote:
The problem is creating the gpart(8) partition scheme on the md(4)
device.
Below follows script(1) output of what the make-memstick.sh script does:
Script started on Sun Jun 9 00:41:08 2013
root@snap:/snap/releng # chroot /snap/releng/10-i386-snap
roo
On Sun, Jun 09, 2013 at 05:01:00AM +0900, Hiroki Sato wrote:
> gj> Because the userland is 32-bit and the kernel is 64-bit, "something"
> gj> goes wrong, but interestingly not wrong enough that the script fails
> gj> entirely. So, the paritions appear to be created, but in reality, they
> gj> are
On Sat, Jun 08, 2013 at 02:18:48PM -0500, Nathan Whitehorn wrote:
> On 06/08/13 14:17, Glen Barber wrote:
> > On Sat, Jun 08, 2013 at 12:10:16PM -0700, Tim Kientzle wrote:
> >> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
> >>
> >>> On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
>
On 06/08/13 14:17, Glen Barber wrote:
> On Sat, Jun 08, 2013 at 12:10:16PM -0700, Tim Kientzle wrote:
>> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
>>
>>> On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
> Has anyone else tried the i386 memstick and having the same problem?
>>>
Tim Kientzle wrote
in <926ef579-8ac9-4a98-8a81-4e978a627...@kientzle.com>:
ti>
ti> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
ti>
ti> > On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
ti> >>> Has anyone else tried the i386 memstick and having the same problem?
ti> >>>
ti> >>
t
Glen Barber wrote
in <20130608173411.gd13...@glenbarber.us>:
gj> On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
gj> Because the userland is 32-bit and the kernel is 64-bit, "something"
gj> goes wrong, but interestingly not wrong enough that the script fails
gj> entirely. So, the
On Sat, Jun 08, 2013 at 12:10:16PM -0700, Tim Kientzle wrote:
>
> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
>
> > On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
> >>> Has anyone else tried the i386 memstick and having the same problem?
> >>>
> >>
> >> Hmm. Thanks for the re
On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
> On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
>>> Has anyone else tried the i386 memstick and having the same problem?
>>>
>>
>> Hmm. Thanks for the report. I'll take a look at the logs for i386, but
>> they are generated the sa
- Original Message -
From: "Dan Mack"
To: "Steven Hartland"
Cc:
Sent: Saturday, June 08, 2013 6:38 PM
Subject: Re: should TRIM be working on my ZFS L2ARC devices?
On Sat, 8 Jun 2013, Steven Hartland wrote:
Does the Vertex 4 and Intel 520 not work with TRIM on FreeBSD or is
some
On Sat, 8 Jun 2013, Steven Hartland wrote:
Does the Vertex 4 and Intel 520 not work with TRIM on FreeBSD or is
something else going on here?
Connected to an controller which supports BIO_DELETE yes they
should.
Check with:
camcontrol identify ada0
Feature Support Enab
On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
> > Has anyone else tried the i386 memstick and having the same problem?
> >
>
> Hmm. Thanks for the report. I'll take a look at the logs for i386, but
> they are generated the same way as the amd64, so in theory should not
> have any
- Original Message -
From: "Dan Mack"
To:
Sent: Saturday, June 08, 2013 4:56 PM
Subject: should TRIM be working on my ZFS L2ARC devices?
Hiya,
Hopefully a simple question on TRIM + ZFS,
I have a couple L2ARCs for a zpool on a test box, two different SSDs:
ada0 at ahcich0 bus 0 s
Hiya,
Hopefully a simple question on TRIM + ZFS,
I have a couple L2ARCs for a zpool on a test box, two different SSDs:
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: ATA-9 SATA 3.x device
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 122
13 matches
Mail list logo
