Re: Growfs Vinum on 5.2-RELEASE
Greg 'groggy' Lehey wrote: What file system? UFS 1 or UFS 2? growfs is suffering a bit from lack of love at the moment. It might be worth putting in a PR. Thanks for the response, File system UFS2 (with softupdates, if that matters?). I've sort of worked around the issue at the moment (backed up, re-created the filesystem on vinum volume from scratch, and restored), but perhaps a PR would help others having the same problem. --Michael. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Growfs Vinum on 5.2-RELEASE
I have followed the method advocated by Drew Tomlinson on this list (October 2002) to create a Vinum volume without losing data. Everything worked ok for the first drive... and then I added the second, and grew the file system using growfs ... and then added the third subdisk to the plex, and tried to growfs again, and got the following message: # growfs -N /dev/vinum/data new file systemsize is: 195366077 frags Warning: 157556 sector(s) cannot be allocated. growfs: 381497.4MB (781306752 sectors) block size 16384, fragment size 2048 using 2076 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. with soft updates super-block backups (for fsck -b #) at: 625120832, 625497184, 625873536, 626249888, 626626240, 627002592, 627378944, 627755296, 628131648, 628508000, 628884352, 629260704, 629637056, 630013408, ... etc ... 775285280, 775661632, 776037984, 776414336, 776790688, 777167040, 777543392, 777919744, 778296096, 778672448, 779048800, 779425152, 779801504, 780177856, 780554208, 780930560 growfs: bad inode number 1 to ginode # Here's my vinum configuration summary: # vinum list 3 drives: D d0 State: up /dev/ad7s1e A: 0/190782 MB (0%) D d2 State: up /dev/ad6s1e A: 0/76319 MB (0%) D d1 State: up /dev/ad4s1e A: 0/114473 MB (0%) 1 volumes: V dataState: up Plexes: 1 Size:372 GB 1 plexes: P data.p0 C State: up Subdisks: 3 Size:372 GB 3 subdisks: S data.p0.s0 State: up D: d0 Size:186 GB S data.p0.s1 State: up D: d1 Size:111 GB S subdisk2State: up D: d2 Size: 74 GB I'm running 5.2-RELEASE, with kernel compiled from RELEASE source to include IPFW. Fairly standard stuff. Is something broken or am I doing something wrong?? Thanks, Michael. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: need some advice on MTA
Regarding the qmail-ldap port assuming I was building a box from scratch, could this port be installed on its own, or is it a 'patch' to an existing (presumably working) qmail installation? The description for this port isn't terribly clear in this regard. Thanks -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Frank Tegtmeyer Sent: Wednesday, 5 February 2003 9:19 PM To: sweetleaf Cc: freebsd-questions Subject: Re: need some advice on MTA sweetleaf [EMAIL PROTECTED] writes: Thanks again, Sir. The only other question would be: Is there a good admin utility for postfix such as the one for qmail. I cannot answer this - I didn't use Postfix extensively. usersmaybe add the user to a databas and the server finds it there. That's right. Relational databases or LDAP are common for such tasks. Vpopmail can use both and there is also a specialized LDAP-patch for qmail that provides additional features besides central account management. Frank To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: Samba and XP?
XP Home will not 'log into' ANY server-based network (NT4 domain model OR Active Directory). However, this does not mean you can't access samba shares on other machines. ie. it supports workgroup networking but not domain networking. Login to the local XP Home box, browse on the network to find the SMB server you want, and open it up. The XP Home box will attempt to authenticate using the local user's username and password: if that fails, it will pop up a box asking for a valid username and password. This should work just fine. XP Home CAN also access shares on servers that are part of a domain, using this same method. The only difference is that the username and password used must be valid on the domain. BTW: just to make it clear, if the credentials used to login to the local XP Home box exist on the SMB server, the user will be let straight through without being asked for another password. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jason Hunt Sent: Sunday, 2 February 2003 9:33 AM To: Bill Moran Cc: John Wilson; [EMAIL PROTECTED] Subject: Re: Samba and XP? On Fri, 31 Jan 2003, Bill Moran wrote: There's an XP machine right behind me that talks to our Samba server just fine. Just don't configure Samba to be a domain server. And, it does work just fine under domain systems as well. Samba just doesn't do active directory yet. OT, but my understanding is that indows XP Home Edition will not log in to NT4-based (SMB-only) networks, but only Windows 2000 (Active Directory) networks. However, Windows XP Professional will log in to both. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: Subnetting or Bridging to secure different dapartments on our School LAN?
Martyn Hill wrote: Windows XP clients, which seem intent on discovering everything on the network and adding it to their own browse lists...) FYI: you can turn this 'feature' off -- it's designed for people setting up networks with just a couple of PCs in a small office. Start up Explorer, Tools -- Folder Options, View, un-check the Advanced setting 'Automatically search for network folders and printers'. There's probably a registry setting you can modify easier than this to do it on multiple machines. --- Michael Ritchie To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: round robin routing - how?
I have something similar working with a Squid cache performing the load balancing. Just set it up to have two upstream caches, then set two static routes - one that says traffic to upstream cache 'A' goes through the first adsl link, and cache 'B' should pass through the other. Seems to work ok for http/ftp traffic (anything that Squid handles)... but any extra traffic will all go through one nominated default route. (But if anyone can point me in the direction Rob wants to go, I would really appreciate that). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rob O'Donnell Sent: Monday, 20 January 2003 7:23 PM To: [EMAIL PROTECTED] Subject: round robin routing - how? Hi there! I've had a good google for this, but not come up with anything significant... My LAN has two available route to the internet - a FreeBSD box with an ADSL modem, (192.168.0.9) and a hardware ADSL router (192.168.0.10) . Two seperate ADSL lines, both the the same ISP as it happens (though am moving one of them shortly.) I can set up the clients individually with one or the other address as default gateway, and each has full access to the 'net at the maximum bandwidth of one line. Is it possible under FreeBSD to set up some sort of round-robin router - I have another hardware ADSL router available, and am not adverse to sticking a couple more network cards in the FreeBSD box if necessary - what I was envisaging was the FreeBSD machine is default gateway for all clients on the lan, and it then routes out to the 'net via either hardware router - so any clients that wants faster bandwidth can get it, as long as they use multiple connections and don't expect any one of them to go over the 512K of one ADSL line. Basically, I want something that does the same job as the Nexland pro800 turbo: http://www.nexland.com/turbo.cfm I've seen references to ng_one2many, but the examples look like they tie multiple adapters together such that they operate as one adapter with one address on one LAN - would this work if i link two adapters directly and independently to two routers and set them up identically? I've also seen references that (at least some versions of) Linux can have multiple default gateways and just use them in sequence. I don't want to have to swap over though... Many thanks in advance, Rob, -- APH Computers Ltd. Tel: 0161-442 2603 Fax: 0161-443 1162 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: Multiple network cards with IP addresses in the same network
I realise that this question has gone on further than the point at which I am replying, but I believe it is around here that everything seems to go astray. From my fairly primitive understanding of the TCP stack in FreeBSD, it would seem that in the case of two network cards being on the same subnet, one is designated as the 'primary' card (if you like) -- in this case, 192.168.0.1, and the other the 'secondary' card -- 192.168.0.2. The primary card is assigned the address 192.168.0.1/24, and will be used to send data to that designated subnet, and receive packets as per normal to its assigned ip address. The secondary card (with the address 192.168.0.2/32) will only be used for receiving data, because the subnet mask does not allow packets to be sent to any address other than that card itself. Linux must therefore use another means by which to determine which interface is used to send packets: my guess would be (in the given example, the eth0 interface, whilst the eth0:0 'alias' is only used to receive data?) As for the gateways, AFAIK, since two devices can only communicate within their own subnets, an interface must be assigned a valid IP address in the same subnet as the router, so that interface can communicate WITH the router itself, which can then route the packets to another wan/lan/whatever. Regards, Michael -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dax Eckenberg Sent: Tuesday, 14 January 2003 12:44 AM To: Anand Buddhdev Cc: [EMAIL PROTECTED] Subject: Re: Multiple network cards with IP addresses in the same network I have addresses 192.168.0.1 and 192.168.0.2. I want to run different services on the 2 different IP addresses. In a linux system, I do: ifconfig eth0 192.168.0.1 netmask 255.255.255.0 ifconfig eth0:0 192.168.0.2 netmask 255.255.255.0 So that I have 2 different addresses bound to the same interface. On FreeBSD, if I do: ifconfig fxp0 192.168.0.1 netmask 255.255.255.0 ifconfig fxp0 192.168.0.2 netmask 255.255.255.0 alias That fails. It should fail, you should enter: # ifconfig fxp0 192.168.0.2 netmask 255.255.255.255 alias In this situation you can ignore the /32 netmask, it will act as /24. The ifconfig manpage states that a nonconflicting netmaks must be used for the alias, and suggests to use 0x. I don't understand why, because I don't see why one network interface cannot have more than one address bound to it within the same network. If I use a /32 netmask for the alias address, how will the kernel respond to arp requests for that alias address? arp requests for .2 will be handled properly by the kernel as if it were /24. 2. Adding a second IP to a *different* network card in the same server does not work if the second IP is within the network of the first one. Because it breaks routing and the basic concept of IP addys and netmasks. If you have two NICs on the same network, how is the kernel supposed to route packets? I still don't understand. In a linux system I can do: route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.0.254 dev eth0 route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.0.254 dev eth1 To my knowledge, this is a Linux feature. Solaris, *BSD, and others don't let you specify the network interface when you add a route. I know for a fact under Solaris that when you have 2 interfaces which live in the same subnet, the interface with the lowest numbered IP will be the interface used for outbound traffic. All I want to do is to have 2 different IP addresses on each of the different interfaces in the server, where the addresses are in the same network. I can do it in linux. Why can't I do it in FreeBSD? Good question. I'd defer this anwser to someone a bit more intimate with FreeBSD's IP stack and routing. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: any advice before I buy a printer for FreeBSD?
I'll back up the case against Lexmark. Many of their larger laser models attempt to do both PCL and PS, as well as some other languages. Unfortunately, they don't seem to have licensed the full PCL or PS code, and their emulation isn't the best. Many pages (especially pages with complex font varieties) will fail to render properly. Just a heads-up, from my experience with Lexmark printers ... of course, I'd never use much other than a HP if I could help it. (Some of the larger Canon models seem ok too) Die, Xerox, Die. m To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Upgrading to 4.7-RELEASE
I am currently working on two FreeBSD 4.6.2 servers, and wish to upgrade to 4.7-RELEASE. I have tried to find information about performing this task, but am having trouble trying to grasp exactly what each distribution type of FreeBSD means. -STABLE can be upgraded to using the (well documented) cvsup, make buildworld, mergemaster etc process, as can -CURRENT, but it would seem to me that -RELEASE is given out only as ISO images, as far as I can see. Is it possible to upgrade a 4.6.2 FreeBSD box to 4.7-RELEASE using the cvsup/make buildworld procedure, or am I better off downloading the mini-ISO or floppy disk images and running a Sysinstall upgrade from there? Is what I am wanting to do a waste of time (ie. should I just go straight to 4.7-STABLE? -- please don't ask why upgrade to 4.7-RELEASE ... I just want to know how to do it, should I some day need it) Regards, Michael Ritchie ps. apologies if it looks like my '-stable, -release and -current's look like i'm yelling -- copied them off the fbsd ftp site. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
