On Wed, Oct 21, 2009 at 14:11, Kris Weston wrote:
> been looking for months now, trawled google no help, i just dont understand.
> do you need a GPT table with zfs ?
> i have a pentium D 3ghz (running 64bit stable 7.2) and i cant seem to import
> my zpool into it
> exported fine on solaris , its d
On Thu, Oct 22, 2009 at 21:38, Pyun YongHyeon wrote:
> On Thu, Oct 22, 2009 at 09:18:15PM +0200, Milan Obuch wrote:
>> On Thursday 22 October 2009 21:05:39 Mike Tancsa wrote:
>> > At 02:22 PM 10/22/2009, Marius N?nnerich wrote:
>> > >Hi Pyun, all,
>> > >
>> > >today I installed FreeBSD 8-STABLE r1
[ originally sent to geom, but am throwing it open to a wider
audience as I didn;t get any replies there]
I am using 7.2-STABLE from October 7th on all amchines, but this
has been going on a while. Very simply I am mirroring together a pair
of discs, one local, one remote. The remote disc is acces
thanks for replying - my problem just got worse.
i used to be able to import and see the pools by typing zpool import
and then the specific name of the pool, in this case 'lakez'
that used to work and i used to be able to see the solaris pool
(although it gave me the error GPT table corrupt which i
Hi,
On Fri, Oct 23, 2009 at 11:56:24AM +0100, Pete French wrote:
> If the remote diisc is actually on a very close machine - e.g. a server
> plugged into the same ether net - then all works fine. If I make
> the remote disc somewhere actually substantially further away on the
> nbetwork, however,
> Just a wild guess, have you tried to set kern.geom.mirror.timeout to a
> higher value?
Yes, I tried values all the way up to 600, no effect at all - plus the
failure comes way before that timeout value (which is in seconds I assume).
-pete.
___
freeb
On Wed, 2009-10-21 at 13:11 +0100, Kris Weston wrote:
> been looking for months now, trawled google no help, i just dont understand.
> do you need a GPT table with zfs ?
> i have a pentium D 3ghz (running 64bit stable 7.2) and i cant seem to import
> my zpool into it
> exported fine on solaris , it
On Thursday 22 October 2009 11:07:23 am Johan Hendriks wrote:
> Hello all
> I just installed FreeBSD 8.0RC1 AMD64 on my new HP Proliant ML150 G6
> server.
> It fails to detect the Broadcom network interface.
>
>
>
> Pciconf -lv gives me the following.
>
> no...@pci0:4:0:0:class=0x02000
On Thursday 22 October 2009 3:17:38 pm pluknet wrote:
> Hi.
>
> I saw this panic just onсe during system shutdown, which
> runs under VirtualBox. Sorry, I don't remember more details.
>
> Unread portion of the kernel message buffer:
> ad0: FAILURE - device detached
> g_vfs_done():ad0s1e[WRITE(off
On Thursday 22 October 2009 11:07:23 am Johan Hendriks wrote:
>> Hello all
>> I just installed FreeBSD 8.0RC1 AMD64 on my new HP Proliant ML150 G6
>> server.
>> It fails to detect the Broadcom network interface.
>>
>>
>>
>> Pciconf -lv gives me the following.
>>
>> no...@pci0:4:0:0:cl
And one adition:
I also have an external harddisk /dev/da1s1 which I labled with "backup"
with RC1. I unfortunally got a /dev/ufs/backup as well as
a /dev/ufs/backupd for the 4th partition of the 1st slide /dev/da1s1d.
I wanted to fix this (label da1s1d as backup) and booted into the single
user
Hi,
I updated my RC1 box now to the latest RELENG_8 code to get my gmirror
+glabel setup working.
Since gjournal was now supposed to work as well I set this up once more.
This was not so easy as I thought because cleaning the metadata on my
previously journaled filesystems (but not working because
On Fri, Oct 23, 2009 at 10:55 AM, Oliver Lehmann wrote:
> And one adition:
>
> I also have an external harddisk /dev/da1s1 which I labled with "backup"
> with RC1. I unfortunally got a /dev/ufs/backup as well as
> a /dev/ufs/backupd for the 4th partition of the 1st slide /dev/da1s1d.
>
> I wanted
Adam Vande More wrote:
> You want clear for changes to persist.
Yeah tried this too without much success - how should I proceed?
r...@nudel /root> ls -l /dev/ufs/backup* /dev/da1*
crw-r- 1 root operator0, 98 Oct 23 18:26 /dev/da1
crw-r- 1 root operator0, 101 Oct 23 18:26 /de
On Fri, Oct 23, 2009 at 11:29 AM, Oliver Lehmann wrote:
> Adam Vande More wrote:
>
> > You want clear for changes to persist.
>
> Yeah tried this too without much success - how should I proceed?
>
> r...@nudel /root> ls -l /dev/ufs/backup* /dev/da1*
> crw-r- 1 root operator0, 98 Oct 23
Hi Adam,
Adam Vande More wrote:
> sysctl kern.geom.debugflags=17
I also tried this in the meantime. The behaviour is still the same. I
also attached the disk to a FreeBSD 7.2 system - same problem:
r...@kartoffel olivleh1> glabel status
Name Status Components
ufsid/49f8856ee
I believe I found a problem with the ULE scheduler - At least the fact that
there is a problem, but I'm not sure where to go from here. The system locks
all processes, but doesn't panic, so I have no output to give.
I was able to duplicate this on three different machines and solved it by
s
On Fri, Oct 23, 2009 at 2:46 PM, Jaime Bozza wrote:
> I believe I found a problem with the ULE scheduler - At least the fact that
> there is a problem, but I'm not sure where to go from here. The system
> locks all processes, but doesn't panic, so I have no output to give.
>
> I was able to du
On 10/23/09, Jaime Bozza wrote:
> I believe I found a problem with the ULE scheduler - At least the fact that
> there is a problem, but I'm not sure where to go from here. The system
> locks all processes, but doesn't panic, so I have no output to give.
>
> I was able to duplicate this on three
> Try adding this or changing these items in lighttpd.conf:
>
> ## FreeBSD!
> server.event-handler = "freebsd-kqueue"
> server.network-backend= "writev"
Scott,
Lighttpd was already using freebsd-kqueue, but I added the writev
network-backend and the problem went away. With this addit
On Fri, Oct 23, 2009 at 04:28:59PM -0400, Dylan Cochran wrote:
> On 10/23/09, Jaime Bozza wrote:
> > I believe I found a problem with the ULE scheduler - At least the fact that
> > there is a problem, but I'm not sure where to go from here. The system
> > locks all processes, but doesn't panic,
er boot only one device per PM was detected (I have two
> hooked up at the moment, 5 drives on one, 1 on the other). However,
> about two minutes later all of the drives showed up!
I've just committed to HEAD new reset sequence for siis. Try please new
HEAD with new patch and show
Jaime Bozza wrote:
[snip]
> The additional information I have (over the PR) is that:
> 1) Files over 64K cause the problem, not just larger files
I thought it was over 1 MB or so. But maybe I'm wrong. ISTR that I
couldn't trigger it with some images of around 70K.
> 2) switching over to SCHED_4BSD
Hi there,
I have a system with a couple of Western Digital "MyBook"
USB2 drives connected to it, and have started seeing some odd
behaviour that I am not sure how to identify the cause of.
Perhaps someone could offer a suggestion or two?
The behaviour that I've noticed (and I can't remember any
p
24 matches
Mail list logo
