On Wed, Feb 17, 2010 at 7:49 PM, Chris wrote:
> As a follow-up to this, I rebuilt world and kernel and updated my
> system to the latest 8.0-STABLE. I'm still seeing the problem and I
> can still get around it by choosing my hard drive from the F12 boot
> menu. I did notice that the bootloader no
As a follow-up to this, I rebuilt world and kernel and updated my
system to the latest 8.0-STABLE. I'm still seeing the problem and I
can still get around it by choosing my hard drive from the F12 boot
menu. I did notice that the bootloader now says it's ZFS enabled
whereas it didn't while on 8.0-R
My r203753 amd64 laptop falls into the deadlock situation
every night while running periodic daily script. I am pretty
certain this is related to ZFS.
I have enabled DEADLKRES in the kernel. I even have
a separate dump partition (not used for swap).
Indeed, the kernel deadlock detector gets tri
On Monday 15 February 2010 2:49:32 pm Matthew Fleming wrote:
> We've seen LOR #185 on http://sources.zabbadoz.net/freebsd/lor.html
> locally on and off since October 2007. This patch has been compiled but
> I don't have a reliable way to repro the LOR so it's not been properly
> tested.
>
> If so
How's this for bizarre? If I hit F12 to bring up the boot menu and
select my hard drive, it boots just fine! If I don't do that, with
8.0-STABLE installed, I get the same lba error 1 errors
as well as the "ZFS: i/o error - all block copies unavailable" error.
Time to call in an exorcist...
On W
On Wed, Feb 17, 2010 at 01:12:53PM -0800, Xin LI wrote:
> Hi,
>
> On Sun, Feb 14, 2010 at 10:20 AM, Gavin Atkinson
> wrote:
> >> /mnt: write failed, filesystem is full
> >> gzip: write: No space left on device
> >> gzip: output file: randomfile.gz wrong size (1673592832 != -1), deleting
> >> gzip
Hi,
On Sun, Feb 14, 2010 at 10:20 AM, Gavin Atkinson
wrote:
>> /mnt: write failed, filesystem is full
>> gzip: write: No space left on device
>> gzip: output file: randomfile.gz wrong size (1673592832 != -1), deleting
>> gzip: leaving original randomfile
>> 0.000u 85.063s 1:25.10 99.9% 0+0k 1244
On Wed, Feb 17, 2010 at 12:40 PM, Pegasus Mc Cleaft wrote:
> Hello Chris, Scott & Current
>
> I use gptzfsboot on my AMD64 (current) machine all the time and also on
> my laptop. I am not sure if this will cause the problem you are seeing but I
> know I ran into a lot of trouble depending o
On Wed, February 17, 2010 09:46, Chris wrote:
> Ok, went back to my 8.0-RELEASE memstick image and after playing with
> the GPT settings a little and dd'ing all zeros to the disk first, I
> get a little farther this time. I'm seeing the following:
>
> -
> BTX loader 1.0
Pegasus,
Thanks for the tip. I'll give it a shot. If it is the case, then the
RootOnZFS wiki guides need to be updated to account for that. They all
currently say to use vfs.root.mountfrom="zfs:zroot" in loader.conf
Thanks,
Chris
On Wed, Feb 17, 2010 at 1:40 PM, Pegasus Mc Cleaft wrote:
> Hello
Chris,
One other thing I just thought of...
On all my machines, I have never used the /dev/gpt/ device.. I have
always used the absolute name /dev/ada0p3, etc..
Peg
On Wednesday 17 February 2010 18:45:47 Chris wrote:
> Pegasus,
>
> Thanks for the tip. I'll give it a shot.
Hello Chris, Scott & Current
I use gptzfsboot on my AMD64 (current) machine all the time and also on
my laptop. I am not sure if this will cause the problem you are seeing but I
know I ran into a lot of trouble depending on what type of pool I was
creating.
I believe this is co
On Wed, Feb 17, 2010 at 10:18 AM, Chris wrote:
> Shouldn't those bug fixes have been included in CURRENT? If so, my
> original post shows the problems there. I've also tried using the
> 8.0-STABLE snapshot dvd1 and got the same errors I got when using
> CURRENT. Again, not sure why this worked on
Shouldn't those bug fixes have been included in CURRENT? If so, my
original post shows the problems there. I've also tried using the
8.0-STABLE snapshot dvd1 and got the same errors I got when using
CURRENT. Again, not sure why this worked on my desktop box and is
failing on the laptop. I'll try co
On Wed, Feb 17, 2010 at 7:46 AM, Chris wrote:
> Ok, went back to my 8.0-RELEASE memstick image and after playing with
> the GPT settings a little and dd'ing all zeros to the disk first, I
> get a little farther this time. I'm seeing the following:
>
> -
> BTX loader 1.
On Wed, Feb 17, 2010 at 10:01:13AM -0700, M. Warner Losh wrote:
> In message: <20100217152557.gw43...@cicely7.cicely.de>
> Bernd Walter writes:
> : Not sure if this is ARM related or not.
>
> ...
> : *** Signal 11
>
> Silly question: do you have enough swap space enabled?
First try
Hi mav!
I got a OpenRD-client (Marvell 88F6281 SoC), and I'm tring to
make mvsata(4) ATA_CAM, like following:
based on sys/arm/conf/DB-88F6XXX
- - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
# SATA
#device ata
#device atadisk
dev
In message: <20100217152557.gw43...@cicely7.cicely.de>
Bernd Walter writes:
: Not sure if this is ARM related or not.
...
: *** Signal 11
Silly question: do you have enough swap space enabled?
Warner
___
freebsd-current@freebsd.org mailing
Ok, went back to my 8.0-RELEASE memstick image and after playing with
the GPT settings a little and dd'ing all zeros to the disk first, I
get a little farther this time. I'm seeing the following:
-
BTX loader 1.00 BTX version is 1.02
Consoles: internal video/keyboard
Not sure if this is ARM related or not.
`sh cflags "optimize='-O -pipe -mcpu=arm9'" opmini.o` -DPIC -fPIC
-DPERL_EXTERNAL_GLOB opmini.c
CCCMD = cc -DPERL_CORE -c
-DAPPLLIB_EXP="/usr/local/lib/perl5/5.10.1/BSDPAN" -DHAS_FPSETMASK
-DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -fsta
Doug,
Haven't tried with different GPT parameters so I guess I could try
that. It's just odd since that same guide worked for me without a
hitch on my desktop machine. I'll try that as well as dd'ing the drive
completely.
Thanks,
Chris
On Tue, Feb 16, 2010 at 10:36 PM, Doug Poland wrote:
> On 2
21 matches
Mail list logo
