Re: dd as an imaging solution.

2007-02-05 Thread Dominic Marks
On Sat, 03 Feb 2007 19:43:42 -0500
Sean Bryant [EMAIL PROTECTED] wrote:

 Several months ago I was using Freesbie 1.x to dd a harddrive across the 
 network as a drive duplication effort. This worked 7 computers got the 
 image. I'm trying to do this again so I got the new Freesbie release 2.0 
 and fired it up across the computers and tried something simple such as:
 
 dd if=/dev/ad0 bs=1m | nc othercomputer 1 on the image provider
 
 nc -l 1 | dd of=/dev/ad0 bs=1m on the computer to receive the image.
 
 I received an operation not permitted. My first thought was they must be 
 mounted. a quick check, and it seems they weren't.
 Next, am I really root? And sure enough I was. After a bit of discussion 
 in #freesbie on freenode got me to set kern.geom.debugflags to 16 and I 
 was able to write to ad0 like I had previously done. Yet when I tried to 
 write to an individual slice I was presented with the same error.
 
 Anyone have any clue ? The eventual goal is to have a mass imaging all 
 at once with dd, nc and tee

Check out G4U (NetBSD based)

 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to [EMAIL PROTECTED]

Dominic
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Changing portsnap servers

2007-02-05 Thread Daniel O'Connor
On Monday 05 February 2007 17:41, Phillip Ledger wrote:
 I have also tryed vairiose combination of the path on the server (e.g.
 SERVERNAME = mirror.internode.on.net/pub/FreeBSD/) to where the snapshot
 is located.howver these result in an error message bad flag in
 substituete command

1) I don't think Internode provide a portsnap mirror
2) You can just use the -s argument to portsnap to pick a mirror.

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


pgpnNcKd4GlZg.pgp
Description: PGP signature


Help with QLogic FC problem diagnosis (da0:isp0:0:0:0): lost device

2007-02-05 Thread Eduardo Meyer

Hello gentlemen,

I have a QLogic FC card in a FreeBSD, connected to a CX300 storage
which sometimes looses connection with no aparent reason. If someone
had lived a similar problem or know of something that would help
diagnose the cause, I would like to hear.

When the problem happens all I get in the logs is:

Feb  5 01:01:37 mailsrvr kernel: isp0: Name Server Database Changed
Feb  5 01:01:37 mailsrvr kernel: isp0: Firmware State Config Wait-Ready
Feb  5 01:01:37 mailsrvr kernel: isp0: Target 126 (Loop 0x7e) Port ID
0xfe (role (none)) Arrived
Feb  5 01:01:37 mailsrvr kernel: Port WWN 0x200500051e034ad8
Feb  5 01:01:37 mailsrvr kernel: Node WWN 0x10051e034ad8
Feb  5 01:01:37 mailsrvr kernel: isp0: 2Gb link speed/s
Feb  5 01:01:37 mailsrvr kernel: isp0: Loop ID 255, Port ID 0x10500,
Loop State 0x2, Topology 'F Port'
Feb  5 01:01:37 mailsrvr kernel: isp0: Target 255 (Loop 0xff) Port ID
0x10500 (role Initiator) Arrived
Feb  5 01:01:37 mailsrvr kernel: Port WWN 0x21e08b925d0e
Feb  5 01:01:37 mailsrvr kernel: isp0: Name Server Database Changed
Feb  5 01:01:37 mailsrvr kernel: isp0: Firmware State Config Wait-Ready
Feb  5 01:01:37 mailsrvr kernel: isp0: Target 126 (Loop 0x7e) Port ID
0xfe (role (none)) Arrived
Feb  5 01:01:37 mailsrvr kernel: Port WWN 0x200500051e034ad8
Feb  5 01:01:37 mailsrvr kernel: Node WWN 0x10051e034ad8
Feb  5 01:01:37 mailsrvr kernel: isp0: 2Gb link speed/s
Feb  5 01:01:37 mailsrvr kernel: isp0: Loop ID 255, Port ID 0x10500,
Loop State 0x2, Topology 'F Port'
Feb  5 01:01:37 mailsrvr kernel: isp0: Target 255 (Loop 0xff) Port ID
0x10500 (role Initiator) Arrived
Feb  5 01:01:37 mailsrvr kernel: Port WWN 0x21e08b925d0e
Feb  5 01:01:37 mailsrvr kernel: Node WWN 0x20e08b925d0e
Feb  5 01:01:37 mailsrvr kernel: isp0:   Fabric Device @ PortID 0x10400
Feb  5 01:01:37 mailsrvr kernel: isp0:   Fabric Device @ PortID 0x10500
Feb  5 01:01:37 mailsrvr kernel: isp0: Target 0 (Loop 0x1) Port ID
0x1 (role Target) Departed
Feb  5 01:01:37 mailsrvr kernel: Port WWN 0x500601603022db3d
Feb  5 01:01:37 mailsrvr kernel: Node WWN 0x50060160b022db3d
Feb  5 01:01:37 mailsrvr kernel: (da0:isp0:0:0:0): lost device
Feb  5 01:01:37 mailsrvr kernel: isp0: Retained login of Target 1
(Loop ID 0x2) Port 0x10400

and later, FreeBSD freezes (sometimes it panics).

It is not very often that it happens, and it is under completly random
circunstances (sometimes high load, sometimes the lowest load, on
different hours, etc).


--
===
Eduardo Meyer
pessoal: [EMAIL PROTECTED]
profissional: [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Trouble Mounting Seagate HD

2007-02-05 Thread Stephen A. Lewis


I am having issues mounting a USB Seagate 300MB HD any suggestions.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Trouble Mounting Seagate HD

2007-02-05 Thread Oliver Fromme
Stephen A. Lewis wrote:
  I am having issues mounting a USB Seagate 300MB HD any suggestions.

I suggest you let us know what exactly the issues are.
Did you plug it in and it installed Vista on your PC?

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH  Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783
Any opinions expressed in this message are personal to the author and may
not necessarily reflect the opinions of secnetix GmbH  Co KG in any way.
FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

UNIX was not designed to stop you from doing stupid things,
because that would also stop you from doing clever things.
-- Doug Gwyn
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: Trouble Mounting Seagate HD

2007-02-05 Thread Kevin K.
Stephen A. Lewis wrote:
 I am having issues mounting a USB Seagate 300MB HD any suggestions.

Maybe its time to get a new HD? 300 megs is pretty small!

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Help with QLogic FC problem diagnosis (da0:isp0:0:0:0): lost device

2007-02-05 Thread Eduardo Meyer

On 2/5/07, Matthew Jacob [EMAIL PROTECTED] wrote:

Helpful information would be:

  a) Release
  b) Connection Topology

It looks like you're going through a switch. Your short term solution
will be to zone your box and the CX300 together excluding all else.

A longer term solution is for me to MFC the new SAN evaluation code
which is a bit less harsh.


You are right, I am going through a switch.
It is a 6.2-STABLE as of Feb 2nd.

Is this code scheduled to be MFC'd?

--
===
Eduardo Meyer
pessoal: [EMAIL PROTECTED]
profissional: [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


ifconfig carp1 destroy = kernel panic

2007-02-05 Thread Stefan Lambrev

Hi all,

This combination of commands lead my freebsd servers to kernel panic.

ifconfig bge0 192.168.1.1 netmask 255.255.255.0
ifconfig bge0 alias 10.1.1.1 netmask 255.255.255.0
ifconfig carp create
ifconfig carp create
ifconfig carp0 192.168.1.222/24 vhid 1 advskew 0 pass somekey
ifconfig carp1 10.1.1.222/24 vhid 2 advskew 0 pass somekey
- to this point everything is ok -
ifconfig carp1 destroy - at this point this will cause kernel panic.
I tested with ifconfig carp1 delete before destroy but the result is the 
same.


tested on freebsd 6.2 pre-release i386 SMP and freebsd 6.2 release amd64 
SMP - in both cases kernel panic.


This seems very similar to this PR - 
http://www.freebsd.org/cgi/query-pr.cgi?pr=92776


I'm going to test on 6.2 stable from today, but I'm not very optimistic.

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x24
fault code  = supervisor read, page not present
instruction pointer = 0x20:0xc0555bcd
stack pointer   = 0x28:0xe4b77bd4
frame pointer   = 0x28:0xe4b77be8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 14 (swi1: net)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 7m2s
Cannot dump. No dump device defined.
aac0: shutting down controller...done

P.S. should I open new PR or just follow up to pr #92776 ?

--
Best Wishes,
Stefan Lambrev
ICQ# 24134177

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Help with QLogic FC problem diagnosis (da0:isp0:0:0:0): lost device

2007-02-05 Thread Wilko Bulte
On Mon, Feb 05, 2007 at 02:04:58PM -0200, Eduardo Meyer wrote..
 On 2/5/07, Matthew Jacob [EMAIL PROTECTED] wrote:
 Helpful information would be:
 
   a) Release
   b) Connection Topology
 
 It looks like you're going through a switch. Your short term solution
 will be to zone your box and the CX300 together excluding all else.
 
 A longer term solution is for me to MFC the new SAN evaluation code
 which is a bit less harsh.
 
 You are right, I am going through a switch.

I would really recommend to use zoning on a FC fabric, even after Matt
has updated the code zoning is a good idea going forward.

 It is a 6.2-STABLE as of Feb 2nd.
 Is this code scheduled to be MFC'd?
 
 -- 
 ===
 Eduardo Meyer
 pessoal: [EMAIL PROTECTED]
 profissional: [EMAIL PROTECTED]
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to [EMAIL PROTECTED]
--- end of quoted text ---

-- 
Wilko Bulte [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Dell PowerEdge 840 in FreeBSD

2007-02-05 Thread LI Xin
Felippe de Meirelles Motta wrote:
 Hi people,
 
 Somebody already got problems with PERC 5/i controller, stopping during
 the boot ?
 
 Reading the last message, i dont known the possible problem, look:
 
 mfi0: 587 (223981812s/0x0001/-1) - VD 00/0 progress 2% in 48s:
 Background Initialization progress on VD 00/0 is 2.03%(48s)
 mfi0:588 (223981820s/0x/0) - Battery temperature is normal
 mfi0: 589 (223981820s/0x/0) - Current capacity of the battery is
 above hold
 mfid0: MFI Logical Disk on mfi0
 mfid0: 278784MB (578949632 sectors) RAID volume '0' is optimal
 
 My hardware informations are:
 
 Dell Poweredge 840
 BIOS A01
 Raid Controller LSI LOGIC Corporation
 PERC 5/i version 5.0.2-0003
 3 HDs in RAID 5
 
 I tested with FreeBSD 6.1 and 6.2, but, no success!
 
 I read about a possible bug in FreeBSD 6.1 with multiple volumes, but i
 don't find any notice that confirmed this, not even any correction/fix.

Could you please try a verbose boot?  This could provide more
information and can sometimes very helpful for us.

Thanks in advance!

Cheers,
-- 
Xin LI [EMAIL PROTECTED]  http://www.delphij.net/
FreeBSD - The Power to Serve!



signature.asc
Description: OpenPGP digital signature


Re: Help with QLogic FC problem diagnosis (da0:isp0:0:0:0): lost device

2007-02-05 Thread Massimo Lusetti
On Mon, 5 Feb 2007 08:00:30 -0800
Matthew Jacob [EMAIL PROTECTED] wrote:

 Helpful information would be:
 
   a) Release
   b) Connection Topology
 
 It looks like you're going through a switch. Your short term solution
 will be to zone your box and the CX300 together excluding all else.
 
 A longer term solution is for me to MFC the new SAN evaluation code
 which is a bit less harsh.

Sorry, couldn't resist, does this will comprehand support for the new
2460 HBA boards?

-- 
Massimo.run();
A lack of leadership is no substitute for inaction.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Trouble Mounting Seagate HD

2007-02-05 Thread Richard Coleman

Stephen A. Lewis wrote:


I am having issues mounting a USB Seagate 300MB HD any suggestions.


After you plug in the external drive, are you seeing any messages in /var/log/messages that the 
drive has been detected by devd/usbd/whatever?


I have a 500g WD mybook, and all I do is:

1. plug it in and wait a few seconds
2. mount /dev/da0s1d /mnt  (as root)

Not much else to it.

Richard Coleman
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ifconfig carp1 destroy = kernel panic

2007-02-05 Thread Hugo Silva

Stefan Lambrev wrote:

Hi all,

This combination of commands lead my freebsd servers to kernel panic.

ifconfig bge0 192.168.1.1 netmask 255.255.255.0
ifconfig bge0 alias 10.1.1.1 netmask 255.255.255.0
ifconfig carp create
ifconfig carp create
ifconfig carp0 192.168.1.222/24 vhid 1 advskew 0 pass somekey
ifconfig carp1 10.1.1.222/24 vhid 2 advskew 0 pass somekey
- to this point everything is ok -
ifconfig carp1 destroy - at this point this will cause kernel panic.
I tested with ifconfig carp1 delete before destroy but the result is 
the same.


tested on freebsd 6.2 pre-release i386 SMP and freebsd 6.2 release 
amd64 SMP - in both cases kernel panic.


This seems very similar to this PR - 
http://www.freebsd.org/cgi/query-pr.cgi?pr=92776


I'm going to test on 6.2 stable from today, but I'm not very optimistic.

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x24
fault code  = supervisor read, page not present
instruction pointer = 0x20:0xc0555bcd
stack pointer   = 0x28:0xe4b77bd4
frame pointer   = 0x28:0xe4b77be8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 14 (swi1: net)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 7m2s
Cannot dump. No dump device defined.
aac0: shutting down controller...done

P.S. should I open new PR or just follow up to pr #92776 ?

Just for the records, I stumbled upon something similar some time ago 
while testing with a co-worker. We both had 6.2-PRERELEASE installed. I 
cannot remember if the same command sequence led to the panic, but we 
were mimicking each other's commands (with the adequate changes for each 
host of course), and both machines panicked on the same command.


Hugo
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Tab completion working partially

2007-02-05 Thread Firas Kraiem

(Sorry for the double-posting, the last message wasn't sent properly)

Hi

I have problems with the tab-completion in my shell (bash). When there  
is only one choice possible, it works fine (e.g. cd /usr/portab il  
complete correctly to /usr/ports). However, when there is multiple  
choices (e.g. cd /usr/ltab) and bash usually shows a list of all  
possible options, it just exits the shell (Konsole or xterm windo is  
closed and I get thrown back to a login prompt when using a tty). In  
sh or csh, it's even worse : completion doesn't work at all. I'm  
running 6.2-STABLE, any ideas about this ?


Firas

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ifconfig carp1 destroy = kernel panic

2007-02-05 Thread Stefan Lambrev

Hi all,

Anton Yuzhaninov wrote:

Hello Stefan,

You wrote on Monday, February 5, 2007, 7:06:16 PM:

SL ifconfig bge0 192.168.1.1 netmask 255.255.255.0
SL ifconfig bge0 alias 10.1.1.1 netmask 255.255.255.0
SL ifconfig carp create
SL ifconfig carp create
SL ifconfig carp0 192.168.1.222/24 vhid 1 advskew 0 pass somekey
SL ifconfig carp1 10.1.1.222/24 vhid 2 advskew 0 pass somekey
SL - to this point everything is ok -
SL ifconfig carp1 destroy - at this point this will cause kernel panic.
SL I tested with ifconfig carp1 delete before destroy but the result is the
SL same.

It seems to be fixed in CURRENT - src/sys/netinet/ip_carp.c Revision 1.47

  
Sorry if this sound too stupid, but do you think, that if I download 
rev. 1.47 (or latest rev. 1.48)
of src/sys/netinet/ip_carp.c and I recompile the kernel this will/can 
fix the problem ?

Anyway I'm going to test this tomorrow :)

--
Best Wishes,
Stefan Lambrev
ICQ# 24134177

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ifconfig carp1 destroy = kernel panic

2007-02-05 Thread Anton Yuzhaninov
Hello Stefan,

You wrote on Monday, February 5, 2007, 7:06:16 PM:

SL ifconfig bge0 192.168.1.1 netmask 255.255.255.0
SL ifconfig bge0 alias 10.1.1.1 netmask 255.255.255.0
SL ifconfig carp create
SL ifconfig carp create
SL ifconfig carp0 192.168.1.222/24 vhid 1 advskew 0 pass somekey
SL ifconfig carp1 10.1.1.222/24 vhid 2 advskew 0 pass somekey
SL - to this point everything is ok -
SL ifconfig carp1 destroy - at this point this will cause kernel panic.
SL I tested with ifconfig carp1 delete before destroy but the result is the
SL same.

It seems to be fixed in CURRENT - src/sys/netinet/ip_carp.c Revision 1.47

-- 
 Anton Yuzhaninov.


Re[2]: ifconfig carp1 destroy = kernel panic

2007-02-05 Thread Anton Yuzhaninov
Hello Stefan,

You wrote on Monday, February 5, 2007, 9:26:44 PM:

SL Hi all,

SL Anton Yuzhaninov wrote:
 Hello Stefan,

 You wrote on Monday, February 5, 2007, 7:06:16 PM:

 SL ifconfig bge0 192.168.1.1 netmask 255.255.255.0
 SL ifconfig bge0 alias 10.1.1.1 netmask 255.255.255.0
 SL ifconfig carp create
 SL ifconfig carp create
 SL ifconfig carp0 192.168.1.222/24 vhid 1 advskew 0 pass somekey
 SL ifconfig carp1 10.1.1.222/24 vhid 2 advskew 0 pass somekey
 SL - to this point everything is ok -
 SL ifconfig carp1 destroy - at this point this will cause kernel panic.
 SL I tested with ifconfig carp1 delete before destroy but the result is the
 SL same.

 It seems to be fixed in CURRENT - src/sys/netinet/ip_carp.c Revision 1.47

   
SL Sorry if this sound too stupid, but do you think, that if I download 
SL rev. 1.47 (or latest rev. 1.48)
SL of src/sys/netinet/ip_carp.c and I recompile the kernel this will/can 
SL fix the problem ?

ip_carp.c from current can contain code which don't work in RELENG_6
Instead try to merge only this changes to ip_carp.c:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/ip_carp.c.diff?r1=1.46r2=1.47

-- 
 Anton Yuzhaninov.


Re: Dell PowerEdge 840 in FreeBSD

2007-02-05 Thread Felippe de Meirelles Motta

Felippe de Meirelles Motta wrote:

LI Xin wrote:

Felippe de Meirelles Motta wrote:

Hi people,

Somebody already got problems with PERC 5/i controller, stopping during
the boot ?

Reading the last message, i dont known the possible problem, look:

mfi0: 587 (223981812s/0x0001/-1) - VD 00/0 progress 2% in 48s:
Background Initialization progress on VD 00/0 is 2.03%(48s)
mfi0:588 (223981820s/0x/0) - Battery temperature is normal
mfi0: 589 (223981820s/0x/0) - Current capacity of the battery is
above hold
mfid0: MFI Logical Disk on mfi0
mfid0: 278784MB (578949632 sectors) RAID volume '0' is optimal

My hardware informations are:

Dell Poweredge 840
BIOS A01
Raid Controller LSI LOGIC Corporation
PERC 5/i version 5.0.2-0003
3 HDs in RAID 5

I tested with FreeBSD 6.1 and 6.2, but, no success!

I read about a possible bug in FreeBSD 6.1 with multiple volumes, but i
don't find any notice that confirmed this, not even any correction/fix.


Could you please try a verbose boot?  This could provide more
information and can sometimes very helpful for us.

Thanks in advance!

Cheers,


LI Xin,

Thanks, more i dont have physical access in this server. The 
installation is completed successfully, but, in reboot her stopped in 
this message above.


I show then one screenshot so that they see where the system paralyzes:

http://br.geocities.com/lippemotta/P149_05_02_2007.jpg

Thanks again! :)



Hi,

Some friends had problems in opening mine screenshot, then i posted 
again in:


http://main.bh.freebsdbrasil.com.br/~lippe/P149_05_02_2007.jpg

--

Atenciosamente,
Felippe de Meirelles Motta
FreeBSD Brasil LTDA.
http://www.freebsdbrasil.com.br
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Tab completion working partially

2007-02-05 Thread Doug Barton
This message really isn't on topic for -stable, so please restrict 
responses to -questions.


Thanks,

Doug

--

This .signature sanitized for your protection

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: dd as an imaging solution.

2007-02-05 Thread Sean Bryant

Dominic Marks wrote:

On Sat, 03 Feb 2007 19:43:42 -0500
Sean Bryant [EMAIL PROTECTED] wrote:

Several months ago I was using Freesbie 1.x to dd a harddrive across the 
network as a drive duplication effort. This worked 7 computers got the 
image. I'm trying to do this again so I got the new Freesbie release 2.0 
and fired it up across the computers and tried something simple such as:


dd if=/dev/ad0 bs=1m | nc othercomputer 1 on the image provider

nc -l 1 | dd of=/dev/ad0 bs=1m on the computer to receive the image.

I received an operation not permitted. My first thought was they must be 
mounted. a quick check, and it seems they weren't.
Next, am I really root? And sure enough I was. After a bit of discussion 
in #freesbie on freenode got me to set kern.geom.debugflags to 16 and I 
was able to write to ad0 like I had previously done. Yet when I tried to 
write to an individual slice I was presented with the same error.


Anyone have any clue ? The eventual goal is to have a mass imaging all 
at once with dd, nc and tee


Check out G4U (NetBSD based)


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Dominic
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


The only problem I can see here is that multiple parallel reads will 
have serious performance impacts, thus greatly increasing the cloning of 
the disk.


The solution with dd, tee and netcat would just daisy chain the copy 
across the network which would be way faster.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]