I just redo everything, and changed the order of freebsd-zfs and
freebsd-swap. The "Read error" still happens!
On Wed, Jun 15, 2011 at 8:07 PM, Zhihao Yuan wrote:
> On Wed, Jun 15, 2011 at 7:58 PM, Xin LI wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> On 06/15/11 17:42, Zhiha
On Wed, Jun 15, 2011 at 7:58 PM, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 06/15/11 17:42, Zhihao Yuan wrote:
>> Hi,
>>
>> I configured my disk layout according to
>> http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition
>>
>> But I swapped the order of the freebsd-zfs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/15/11 17:42, Zhihao Yuan wrote:
> Hi,
>
> I configured my disk layout according to
> http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition
>
> But I swapped the order of the freebsd-zfs and freebsd-swap. The 4.0G
> freebsd-swap partition appears
I have hardware now, am working on reproducing this. Just curious, do you
have
the em driver defined in the kernel, or as a module?
Jack
On Wed, Jun 15, 2011 at 2:09 AM, Joshua Boyd wrote:
> On Wed, Jun 15, 2011 at 3:57 AM, Jeremy Chadwick
> wrote:
>
> > On Wed, Jun 15, 2011 at 03:14:43AM -040
Hi,
I configured my disk layout according to
http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition
But I swapped the order of the freebsd-zfs and freebsd-swap. The 4.0G
freebsd-swap partition appears first inside the slice.
After that, I write zfsboot on both ada0s2 and ada0s2b, but the boot0
gives
In the kernel. Here's my kernel configuration:
http://pastebin.com/raw.php?i=4JL814m3
On Wed, Jun 15, 2011 at 8:20 PM, Jack Vogel wrote:
> I have hardware now, am working on reproducing this. Just curious, do you
> have
> the em driver defined in the kernel, or as a module?
>
> Jack
>
>
> On We
On Wed, Jun 15, 2011 at 04:44:55PM +0200, Joerg Wunsch wrote:
> As Kostik Belousov wrote:
>
> > Do sysctl security.bsd.map_at_zero=1
>
> Just for the record, this sysctl also makes my really really old utree
> binary work again. The binary dates back to 386BSD 0.0, and I'm only
> keeping it out
2011/6/15 Jeremy Chadwick :
> On Wed, Jun 15, 2011 at 03:57:05PM +0200, Joerg Wunsch wrote:
>> When trying to use doscmd on 8-stable, all I get is:
>>
>> Error mapping HMA, HMA disabled: : Invalid argument
>> Segmentation fault (core dumped)
>>
>> The segfault happens at the end of mem_init(), when
As Kostik Belousov wrote:
> Do sysctl security.bsd.map_at_zero=1
Just for the record, this sysctl also makes my really really old utree
binary work again. The binary dates back to 386BSD 0.0, and I'm only
keeping it out of curiosity:
j@uriah 66% ls -l /usr/local/bin/utree
-rwxr-xr-x 1 bin bin
As Kostik Belousov wrote:
> > So does anyone have an idea
> > why this mmap() call:
...
> > yields an EINVAL now under 8-stable?
>
> Do sysctl security.bsd.map_at_zero=1
Ah, thanks! Now it works. Well, at least it doesn't crash anymore (I
somehow have to fix my boot environment, hopefully I'
Hi Joerg,
Flip security.bsd**.map_at_zero to 1.
On Wed, Jun 15, 2011 at 3:57 PM, Joerg Wunsch <
freebsd-sta...@uriah.heep.sax.de> wrote:
> When trying to use doscmd on 8-stable, all I get is:
>
> Error mapping HMA, HMA disabled: : Invalid argument
> Segmentation fault (core dumped)
>
> The segfa
On Wed, Jun 15, 2011 at 03:57:05PM +0200, Joerg Wunsch wrote:
> When trying to use doscmd on 8-stable, all I get is:
>
> Error mapping HMA, HMA disabled: : Invalid argument
> Segmentation fault (core dumped)
>
> The segfault happens at the end of mem_init(), when the allocated DOS
> memory (which
On Wed, Jun 15, 2011 at 03:57:05PM +0200, Joerg Wunsch wrote:
> When trying to use doscmd on 8-stable, all I get is:
>
> Error mapping HMA, HMA disabled: : Invalid argument
> Segmentation fault (core dumped)
>
> The segfault happens at the end of mem_init(), when the allocated DOS
> memory (which
When trying to use doscmd on 8-stable, all I get is:
Error mapping HMA, HMA disabled: : Invalid argument
Segmentation fault (core dumped)
The segfault happens at the end of mem_init(), when the allocated DOS
memory (which is located at virtual address 0) is attempted to be
written to. Apparently
W dniu 2011-06-15 14:12, Andrey V. Elsukov pisze:
On 15.06.2011 15:43, Bartosz Stec wrote:
As you see I have ada{0-2}p3 labeled as disk{0-2} All labeled partitions have
valid gpt id but
zfs partitions don't have accesible gpt label in /dev/gpt:
It always worked so. Read geom(4) manual page, es
On 15.06.2011 15:43, Bartosz Stec wrote:
> As you see I have ada{0-2}p3 labeled as disk{0-2} All labeled partitions have
> valid gpt id but
> zfs partitions don't have accesible gpt label in /dev/gpt:
It always worked so. Read geom(4) manual page, especially about SPOILING.
> As you see labels w
Hi list,
please take a look at this:
#gpart show
=> 34 80293181 ada0 GPT (38G)
34 128 1 freebsd-boot (64k)
162 2097152 2 freebsd-swap (1.0G)
2097314 76068013 3 freebsd-zfs (36G)
78165327 2127888- free - (1.0G
On Tue, 14 Jun 2011 17:01:21 -0400, Steve Polyack wrote:
I'll just have to adapt and ensure they have the same IP addresses
then.
I have a suspicion that the important part may be the number of IP
addresses on the CARP interface. If CARP sends an advertisement from
each IP alias on a CARP i
On Wed, Jun 15, 2011 at 3:57 AM, Jeremy Chadwick
wrote:
> On Wed, Jun 15, 2011 at 03:14:43AM -0400, Joshua Boyd wrote:
> > I recently updated my server to the latest 8-STABLE, and upgraded to v28
> > ZFS. I have not had these problems on any other version of 8-STABLE or
> > 7-STABLE, which this bo
On Wed, Jun 15, 2011 at 03:14:43AM -0400, Joshua Boyd wrote:
> I recently updated my server to the latest 8-STABLE, and upgraded to v28
> ZFS. I have not had these problems on any other version of 8-STABLE or
> 7-STABLE, which this box was upgraded from some time ago.
>
> Now, during my weekly scr
I recently updated my server to the latest 8-STABLE, and upgraded to v28
ZFS. I have not had these problems on any other version of 8-STABLE or
7-STABLE, which this box was upgraded from some time ago.
Now, during my weekly scrub, I get the following messages and em0 is
unresponsive:
Jun 12 03:07
21 matches
Mail list logo
