Re: antivirus gateway
2009/8/23 Yavuz Maşlak yavuz.mas...@netiletisim.net Hello I wish to use freebsd7.2 as an antivirus gateway. What is an antivirus gateway? Perhaps you need to filter e-mail viruses before the e-mail goes to the delivery server? Please try and make us understand what your situation is and what you want to do/achieve. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ If you have nothing good to say about someone, just shut up!. -- Lucky Dube ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: What should be backed up?
Jeffrey Goldberg wrote: This is one of the several reasons that I use rsync (via rsnapshot). At each increment, it backs up the minimum that is need. With the cost of having a complete backup which duplicates what you would find in a reinstall, you have a complete system. For binaries, I find it much safer/easier to reinstall, then you're sure all dependencies are installed correctly as well as the pkg database is updated correctly. For the rest of the files, having a complete backup I'll have to trace through what differs from the distributed/default configuration etc. Doing that from the start is much easier. And, the default configuration comes with the source, so no need to backup that. Of course this is also because when the recovery stragety is to reinstall, I'll likely upgrade while at it. So I can't assume blindly old default configuration files will work without modifications. BR, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: MD5 Checksum mismatch for netatalk-2.0.4.tar.bz2
On 23 August 2009, at 10:56, andrew clarke wrote: On Sun 2009-08-23 10:24:53 UTC+0200, Vincent Zee (zen...@xs4all.nl) wrote: === Vulnerability check disabled, database not found === Extracting for netatalk-2.0.4,1 = MD5 Checksum mismatch for netatalk-2.0.4.tar.bz2. = SHA256 Checksum mismatch for netatalk-2.0.4.tar.bz2. I'm getting a checksum mismatch here too. This probably means the tarball was modified. I checked the distinfo file and it is the same as on my other machine. On which the update went fine. Solution #1: Use make NO_CHECKSUM=yes, just ignore the mismatch and hope it will build. Solution #2: Copy /usr/ports/distfiles/netatalk-2.0.4.tar.bz2 from your other machine and rebuild. Solution #3: Don't bother building from ports if you already have a working binary on your other machine. Use pkg_create -vb netatalk\*, copy the resulting file to the new machine, then use pkg_add. This assumes the same architecture (eg. i386) on both machines. Hi Andrew, thanks for your answer. I think I'll go with solution number two since the machine have different architectures. /\ Vincent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
what www perl script is running?
Hi all, I noticed this morning that a perl script was using a lot of CPU time on my FreeBSD webserver. By the time I killed it, it had run up 400 mins of system time according to top. However, simply killing 'perl5.8.9' didn't accomplish much, it was back running again moments later. I then rebooted. Once again it is running. According to top, the owner of the process is 'www', which would be lighttpd. So, it appears that lightthp is persistently spawning a perl script.But which one? I don't use perl much, but I do have it enabled in lighttp: [...] ) server.modules = ( mod_access, mod_simple_vhost, mod_accesslog, mod_cgi, mod_rewrite, mod_auth, mod_fastcgi, mod_redirect ) static-file.exclude-extensions = ( .fcgi, .php, .rb, ~, .inc ) cgi.assign = ( .pl = /usr/bin/perl, .cgi = /usr/local/bin/python, .py = /usr/local/bin/python, .sh = /usr/local/bin/bash ) [...] Is there a command like fuser or lsof which can be used to determine what files this perl instance is using? Any other ideas on how to figure out what is going on here? Thanks. uname: FreeBSD 7.0-STABLE i386 -- Colin Brace Amsterdam http://www.lim.nl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: what www perl script is running?
Is there a command like fuser or lsof which can be used to determine what files this perl instance is using? Any other ideas on how to figure out what is going on here? lsof is in the ports. best regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Serial console trouble: loader and login works, but no kernel messages
On Aug 23, 2009, at 23:18, Carl Chave wrote: Did you try booting with the keyboard disconnected from the FreeBSD machine? Perhaps the vidconsole is favored when a keyboard is detected? On a linux box I had, I would get serial output from Grub, lose it during kernel load and then get a login once the OS was up, much like what you describe. I had to add a kernel argument to my Grub config so the kernel would output to the serial port. Did you look here: http://www.freebsd.org/doc/en/articles/console-server/freebsd.html I think 7.2 might be what you are missing but I can't check it myself. On Sun, Aug 23, 2009 at 3:13 PM, Thomas Backmanseren...@exscape.org wrote: On Aug 23, 2009, at 20:25, Tim Judd wrote: On 8/23/09, Thomas Backman seren...@exscape.org wrote: First off: Not subscribed to this list, please make sure to Cc me if you don't reply directly. :) Anyway, I finally got my null modem cable, and plugged in in between a machine running 8.0-BETA2 and one running WinXP using Hyperterminal. My settings: /boot/loader.conf: boot_multicons=YES boot_serial=YES comconsole_speed=115200 console=comconsole,vidconsole /etc/ttys: # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 /usr/libexec/getty std.115200 vt100 on secure /boot.config (which is read properly): -Dh -S115200 Anything wrong in the above? Hyperterminal is set to 115200 bps, 8 bits, no parity, 1 stop bit, and no flow control (if that's the correct translation to English). On the serial console, I go from the screen with the FreeBSD logo, with single-user options etc. (which works fine), and then nothing, until a login tty pops up (which also works fine). The main, if not only, reason I want a serial console is to be able to use it for single user mode, DDB, and so on. All kernel messages, and all rc messages are seen only on the graphics card; the serial console receives nothing but the /boot.config: - Dh ..., the logo screen, and then the login screen, during startup and *nothing* at all during shutdown. Also, I'm able to login and use the system both via the serial console and via the graphics card/ keyboard... Is this supposed to be? I'm not complaining, I just got the impression it was one or the other. Any advice on how to get the kernel/rc messages etc. to the serial console (only or as well)? Regards, Thomas Do you use the VGA/vidconsole at all? A serial-only device (think soekris, ALIX/WRAP boards) that has no VGA will have different requirements than a serial-only device will. Your loader.conf statements are different than mine in the definition that you have more than I do to enable serial. My loader.conf just has one statement: console=comconsole - to feed ALL bootloaders, kernel probing, rc startup on the serial device. /etc/ttys defines the login lines. Though trial and error, I found when you use a dual-setup: comconsole,vidconsole, the first one (comconsole) will get rc output, and vidconsole won't. Of course, you're on 8.0 and I don't run BETAs. So the 8.0 BETA might still be having com port oddities, plus I noticed your ttys line is ttyu0, not ttyd0. Did 8.0 change the serial line device? To enable a serial-only device in my setups: /boot/loader.conf: console=comconsole /boot.config: -D /etc/ttys: # enable serial line, cons25 or vt100, depending if I'm originating from a bsd or windows box. Enabling dual-setups should be just the loader.conf change to dual console. HTH (Sorry for the lack of inline replies.) I do have a graphics card, and ideally I'd like to be able to use both, but serial has higher priority (with serial access, I can use minicom on another *nix box and essentially ssh into DDB, and stuff like that - right now I have to borrow a monitor, and write info down manually if needed, turning my head back and forth). I've tried lots of combinations of console=, including simply 'console=comconsole' and/or combinations of that and -D, -h- -Dh and -P in /boot.config. The extra lines in loader.conf are from the handbook, which says they're needed to use comconsole_speed. It seems they do the same thing as - D and -h, though. Oh, and re: /etc/ttys: Yup, it's ttyuX when using uart(4) which seems to be the default now. Actually, since my last buildworld half an hour ago I'm on 9.0-CURRENT. ;) Also, I made sure to set flags to 0x10 for the serial port as per the handbook (although I did it using loader.conf, not the kernel config); before the change, dmesg didn't mention any flags, but it now does. Didn't help squat, though. Though trial and error, I found when you use a dual-setup: comconsole,vidconsole, the first one (comconsole) will get rc output, and vidconsole won't. This doesn't mirror my experience; comconsole and comconsole,vidconsole appears to be just the same for me. I've never gotten anything except the boot loader and a login prompt over to the serial
Re: what www perl script is running?
On Monday 24 August 2009 10:07:50 Olivier Nicole wrote: Is there a command like fuser or lsof which can be used to determine what files this perl instance is using? Any other ideas on how to figure out what is going on here? lsof is in the ports. and fstat(1) is in the core. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: RAID10 setup
2009/8/24 John Nielsen li...@jnielsen.net You're on the right track, additional comments inline. On Saturday 22 August 2009 06:49:06 am Phil Lewis wrote: This question was asked a few weeks ago, but the original poster must have had their questions amswered. As follow-ups offered further assistance given more detail, I wonder if I could be so bold as to provide that detail for my own circumstances. I have six disks: ad4 - 500MB ad5 - 500MB ad6 - 500MB ad7 - 400MB ad8 - 500MB ad10 - 500MB These are SATA drives, with ad8 and ad10 on a PCIe SATA controller. ad7 was my first disk and currently contains FreeBSD7.2-RELEASE. I've been using that to gain some familiarity with FreeBSD, but it need not be preserved (in fact, I'd rather not preserve it!). When I built the machine, I just plugged the 400GB drive in any old slot, so it can move if that makes sense. When I got the new drives I tried to get identical to the 400GB drive, but couldn't. The 400GB drive currently has a single slice using the full drive. Just make sure you have the disk(s) you plan to boot from on a controller that will boot in your machine. If the controllers have different performance characteristics then you probably want to share the wealth of the better one between multiple mirrors. What I'd like to end up with is a three-way stripe across three two-way mirrors, containing as much of the system as possible. This is certainly do-able. If it were me I'd put the whole OS on the spare change partitions and leave the whole stripe for your serious data consumer(s): /home, /data, possibly /usr/local or some or all of /var, etc. Depends on your intended use of the storage naturally. I understand that you can't boot from a stripe, so some part of some disk will have to be outside the stripe. However, as the stripe will also be limited to the smallest disk, I'm going to have 5 x 100 GB bits left over anyway, so I guess /boot can go on one of these..? Absolutely. I'd make a gmirror of two or three of them and put / on it. If you really want to be minimal w/ your use of the extra space then you could do /boot as you propose. If possible, I'd like set this up pre-install. If it has to be done post-install, or is easier to describe how to do post-install, then that's fine. Either will work. Exactly how you do it depends on how much of the base system you want to end up on the stripe. From here on in, this email becomes speculative. All of the examples I've seen for setting up GEOM stripes and mirrors have used the raw disk as the base-level provider. On the other hand, I've seen nothing that says that the bottom level cannot be a slice, rather than a raw disk, and given the way GEOM works, I suspect this is true. Yes, you can use partitions, slices or any other GEOM providers as members of gstripe, gmirror and friends. My current plan, based on this assumption, is as follows: With my current FreeBSD installation, create 2 slices on each 500GB disk, 1 x ~400GB, 1 x ~100GB (the same size as the slice of my 400GB disk, and the rest of the disk). Boot from the FreeBSD 7.2-RELEASE dvd, and enter fixit mode. I'm not sure which would be best, or even if both are feasible for what I want to do. (I was at this point in my researchwhen I found this post!). From here, kldload geom_stripe and kldload geom_mirror. Then, create the three mirrors: gmirror label -v main0 /dev/ad4s1 /dev/ad5s1 gmirror label -v main1 /dev/ad6s1 /dev/ad571 gmirror label -v main2 /dev/ad8s1 /dev/ad10s1 This should give me /mirror/main0|main1|main2, right? Right. Next create the stripe: gstripe label -v -s 131072 raid10 /dev/mirror/main0 /dev/mirror/main1 /dev/mirror/main2 (that's all one line) If I'm right so far, then hopefully I should be able to boot to the install dvd again (or just rerun sysnstall?), and from there I should be able to choose a slice from outside 'raid10' to mount /boot, and use 'raid10' for everything else. Do I need anything else on a non-striped slice? /boot or equivalent is the only thing required to smell like a normal disk (which gmirror is capable of but gstripe isn't). You may want to use some of the space for swap. The virtual memory system should do its own version of stripe or interleave if you feed it multiple swap devices. Maybe I could even create another mirror: gmirror label -v boot /dev/ad4s2 /dev/ad5s2 and use that to mount /boot, leaving me with s2 on ad6,8 and 10 as 3 spare 100GB slices? Or am I just way off track? You seem to be pretty well on track. It seems you've already parsed the gstripe and gmirror man pages. You should probably look at fdisk(8) and bsdlabel(8) as well in case sysinstall doesn't tie up all your loose ends. Additionally you could just reinstall to a plain disk (or use
Re: ndis driver - freeze on scan
On Mon, Aug 17, 2009 at 04:48:44PM +, Eitan Adler wrote: I created an ndis driver for my wireless card and kldloaded it. When I try ifconfig ndis0 up scan my computer just freezes and it does not find any of the 100 (exaggeration) APs around. This is a broadcom wireless card. -- Eitan Adler Security is increased by designing for the way humans actually behave. -Jakob Nielsen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org What version of FreeBSD is this? If it's 8.x, you have to scan with the wlan0 device. I've seen lots of weird and nasty things happen when trying to manipulate the actual ndis0 device under 8. ifconfig wlan0 create wlandev ndis0 ifconfig wlan0 up scan pgpIYM45ph7vC.pgp Description: PGP signature
Re: RAID10 setup
Thanks to both of you for the encouraging words. I'm going to do little more reading and schedule some time probably on Wednesday to give this a go. I'll feel a lot more conformable for your responses! Cheers Phil Date: Sun, 23 Aug 2009 23:30:52 -0400 From: John Nielsen Subject: Re: RAID10 setup To: freebsd-questions@freebsd.org Cc: Phil Lewis dharm...@gmail.com Message-ID: 200908232330.53118.li...@jnielsen.net Content-Type: text/plain; charset=iso-8859-1 You're on the right track, additional comments inline. ... You seem to be pretty well on track. It seems you've already parsed the gstripe and gmirror man pages. You should probably look at fdisk(8) and bsdlabel(8) as well in case sysinstall doesn't tie up all your loose ... Date: Mon, 24 Aug 2009 10:53:45 +0100 From: chris scott Subject: Re: RAID10 setup To: John Nielsen Cc: Phil Lewis dharm...@gmail.com, freebsd-questions@freebsd.org Message-ID: d36406630908240253h3d6dd048n21468b6b18b41...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 ... When you create the file systems you should also consider laying gjournal on top of the stripe as well. In most cases it will remove the need for having to fsck the file systems when there's a system crash. Quite useful if the filesystem is large. I also like the label the filesystems with glabel so they appear in the fstab as /dev/ufs/root /dev/ufs/usr /dev/ufs/var etc makes life a little easier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: netbooks for freebsd?
thanks. i've looked at both an acer and lenovo models and like the lenovo model better. as for linux... no way.. had too many hack experiences during the early years. that's why i made the switch to bsd. i would like to make my own port (super-port?), build a distro, and dump it onto a machine. haven't tested on virtual machine yet, but think that would be the smartest method. thanks again. On Aug 23, 2009, at 11:39 AM, ill...@gmail.com wrote: 2009/8/19 Jeff Hamann jeff.ham...@forestinformatics.com: I would like to try some experimental software on a netbook. Can somebody recommend a netbook that can do FreeBSD. Late to the discussion, sorry I can't give positive advice, but: I can explicity UNADVISE the (ee?)pc 1005ha Networking (atheros 9285, iirc) might work under ndis, wired (I forget which chipset) doesn't work. I put ubuntu on it, and even _that_ took some hacks. -- -- Jeff Hamann, PhD PO Box 1421 Corvallis, Oregon 97339-1421 541-754-2457 jeff.hamann[at]forestinformatics[dot]com http://www.forestinformatics.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
moving a disk
I am trying to move a 7.2 installation to another computer where it is to be the only OS acting as a server for the lan. On bootup I get the message: Using drive 0, partition 3. And there it hangs. I have tried to rewrite the mbr but that did absolutely nothing. fik ad0 returns: partitions 1,2,3 are UNUSED Parrtition 4 give the cylinder, heads, sectors, blocks stuff The disk did boot up on another box... What should I do? And what information do I need to supply or look for to solve this. I'd rathernot go through another installation even if this is farly elementary. Oh, yes... all my former problems were definitely software related as I have checked and double, triple checked my HDDs and cannot find any problems therewith. TIA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problem with cURL and pipes
Hello all, there seems to be something wrong with sending data through pipes. I'm trying to upload files to an FTP server by piping them to cURL: These work: - curl file-to-send ... - cat file-to-send | curl ... These don't: - gzip file-to-send | curl ... - bzip2 file-to-send | curl ... - cat file-to-send | rev | curl ... The compressed input in this case is about 7 MB, but it only sends up to 2 MB of that. Sometimes nothing, more often something in between. This is on 7-STABLE from this morning, but the same problem existed on 7-STABLE from ten months ago (I upgraded to see if that would fix it). This has worked flawlessly for several months, then started failing last week. Any ideas what might be the reason? Thanks for your help, -- Christian Ullrich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: What should be backed up?
If you have any databases or ldap service, then you want to add those as well, but it is recommended to dump these rather than backup the files themselves. I'm learning a lot from this thread. Thanks for all the suggestions. The paragraph above raises one more question... how to use the backup_script feature of rsnapshot. There is a mysql database on the server I want to backup. At the moment, I have a cron script on the web server that periodically dumps the database into one of the directories that gets backed up. This works fine, but I am about to experiment with the backup_script feature of rsnapshot. I'll be darned if I can find an example in the HowTo or on the web for using backup_script remotely, but I'm hoping it's possible... I'd like to have the backup script on the backup server, rather than the remote server. The difference is small for one server, but if you are backing up several servers, or several hundred servers, it would be much nicer for all the backup configuration and scripts to be on the backup server, rather than scattered around on the net. So, I'm going to take the trial and error approach to getting this to work today, unless someone has actually done this and can provide any information (for example that's impossible... the backup script needs to be on the remote server would save me a lot of work!) Thanks: John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: What should be backed up?
John Almberg wrote: If you have any databases or ldap service, then you want to add those as well, but it is recommended to dump these rather than backup the files themselves. I'm learning a lot from this thread. Thanks for all the suggestions. The paragraph above raises one more question... how to use the backup_script feature of rsnapshot. I don't know your backup_script, but you can just add to it. It is usually possible to give read only remote access, with or without password, from the server where you store your backups. Then all you need is to add a few lines to your script. For ldap, you'll want to create an ldif format dump. For sql, check out the various dump formats. The more sql standard the more secure you are, but it comes at the price of time when recovering data. For sql, you may also consider whether to include statements for dropping existing tables and databases as well as include create statements. It really depends on which disaster you're preparing for. It may be possible to create one dump with drop/create statements to recover database structure, and another dump with data. The reason you'll want to dump ldap/sql data is that you ensure data integrity if your backup coincide with some update of the database. Also, you can use the backup when upgrading or even if you change database say from mysql to postgresql - for this you need as strict sql backup as possible, both allow some shortcuts that are faster for recovery but may be incompatible with other databases. Make the backup verbose, ensure that things like default character set is included in the dump, make sure that binary blobs are dumped in base64 etc... You _can_ do file backup of your databases, it is certainly faster to recover from a file backup, but you run the risk of inconsistencies. The same problem of data inconsistencies can happen with any other file backup: you may wish to temporarily stop local maildelivery while you backup user's mail boxes. Mail will remain in the queue till backup terminates and local mail delivery is reenabled. you may consider not to backup log files, or only files after they have been rotated so they are no longer written to. you may consider locking down user access while home directories are backed up, etc. It all depends on the time required to complete the backup and the normal activity on the systems while you backup. And - don't forget - now that you have everything nicely backed up, you need a data destruction policy to ensure that you don't accidentally keep personal data from old users. BR, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: moving a disk
PJ wrote: I am trying to move a 7.2 installation to another computer where it is to be the only OS acting as a server for the lan. On bootup I get the message: Using drive 0, partition 3. And there it hangs. I have tried to rewrite the mbr but that did absolutely nothing. fik ad0 returns: partitions 1,2,3 are UNUSED Parrtition 4 give the cylinder, heads, sectors, blocks stuff The disk did boot up on another box... What should I do? And what information do I need to supply or look for to solve this. I'd rathernot go through another installation even if this is farly elementary. Oh, yes... all my former problems were definitely software related as I have checked and double, triple checked my HDDs and cannot find any problems therewith. here is what I have found in looking at the disk when it's mounted on another FBSD system through an USB interface: it is mounted on /dev/ad0 fdisk ad0 --- returns partitions 1,2,3 as UNUSED; partition 4 is marked for sysid 166 OpenBSD (this seems to be left over from an installation that was never completed) fdisk ad0s4 --- returns same, except partition 4 is: sysid 165 (FreeBSD,NetBSD/386BSD) I also note that the other functioning FBSD 7.2 has partitions 2-4 as UNUSED and partition 1 has the cylinder parameters. I get the impression that I should use the disklabel editor to change all that but am not familiar with it and am not sure how to use it. Here is what bsdlabel shows: # /dev/ad0s4: #this is the one that does not boot 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 2097152 634.2BSD 2048 16384 28552 b: 2097152 2097215 swap c: 12594897 63unused0 0 # raw part, don't edit d: 2097152 41943674.2BSD 2048 16384 28552 e: 2097152 62915194.2BSD 2048 16384 28552 f: 4204544 83886714.2BSD 2048 16384 28552 partition c: partition extens past end of unit disklabel: partition c doesn't start at 0! disklabel An incorrect partition c may cause problems for standard system utilities # /dev/ad4s1: #this one boots 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 419430404.2BSD 2048 16384 28552 b: 6291456 4194304 swap c: 1563014250unused0 0 # raw part, don't edit d: 6291456 104857604.2BSD 2048 16384 28552 e: 4194304 167772164.2BSD 2048 16384 28552 f: 69206016 209715204.2BSD 2048 16384 28552 g: 66123889 901775364.2BSD 2048 16384 28552 Is there a way to fix this thingy? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Continuous backup of critical system files
Hello all, I'm setting up a firewall using FreeBSD 7.2 and thought that it may not be a bad idea to have a continuous backup for important files like pf and dnsmasq configurations. By continuous I mean some script that would be triggered every few minutes from cron to automatically create a backup of any monitored file if it was modified. I also have a full system backup in place that is executed daily (dump/restore to a compact flash card), so the continuous backup would really be for times when someone makes a mistake editing one of the config files and needs to revert it to a previous state. My initial thought was to create a mercurial repository at the file system root and exclude everything except for explicitly added files. I'd then run something like hg commit -m `date` from cron every 10 minutes to record the changes automatically. Can anyone think of a better way to do this (existing port specifically for this purpose)? Obviously, I need a way to track the history of a file and revert to a previous state quickly. The storage of changes should be as size-efficient as possible. - Max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Continuous backup of critical system files
El día Monday, August 24, 2009 a las 11:57:25AM -0400, Maxim Khitrov escribió: Hello all, I'm setting up a firewall using FreeBSD 7.2 and thought that it may not be a bad idea to have a continuous backup for important files like pf and dnsmasq configurations. By continuous I mean some script that would be triggered every few minutes from cron to automatically create a backup of any monitored file if it was modified. I also have a full system backup in place that is executed daily (dump/restore to a compact flash card), so the continuous backup would really be for times when someone makes a mistake editing one of the config files and needs to revert it to a previous state. My initial thought was to create a mercurial repository at the file system root and exclude everything except for explicitly added files. I'd then run something like hg commit -m `date` from cron every 10 minutes to record the changes automatically. Can anyone think of a better way to do this (existing port specifically for this purpose)? Obviously, I need a way to track the history of a file and revert to a previous state quickly. The storage of changes should be as size-efficient as possible. Hello, We run in my company since many years a FreeBSD based firwall. All modified config files like, rc.conf, ipf.rules, ... have always been on some internal host in CVS, only modified there and SCP'ed to the firewall to make the change there active. After some hardware fault I was once able to do a bare metal restore of the firewall within an hour, just installed the base system and copied over the config from CVS. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Continuous backup of critical system files
2009/8/24 Maxim Khitrov mkhit...@gmail.com Hello all, I'm setting up a firewall using FreeBSD 7.2 and thought that it may not be a bad idea to have a continuous backup for important files like pf and dnsmasq configurations. By continuous I mean some script that would be triggered every few minutes from cron to automatically create a backup of any monitored file if it was modified. I also have a full system backup in place that is executed daily (dump/restore to a compact flash card), so the continuous backup would really be for times when someone makes a mistake editing one of the config files and needs to revert it to a previous state. My initial thought was to create a mercurial repository at the file system root and exclude everything except for explicitly added files. I'd then run something like hg commit -m `date` from cron every 10 minutes to record the changes automatically. Can anyone think of a better way to do this (existing port specifically for this purpose)? Obviously, I need a way to track the history of a file and revert to a previous state quickly. The storage of changes should be as size-efficient as possible. - Max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I rsync all my system files to a filer running zfs. I have a separate zfs fs for every host and then I snapshot the fs after the rsync. We then keep 35 snapshots for retention as we do daily rsyncs. You might want more of a rolling snapshot policy. Keep on for every 10 mins of the last hour, then drop it to hourly for the next 6 hours, then daily, then weekly etc Works quite well. We have also found it handy for forensics as well, when we have had a fault ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Continuous backup of critical system files
2009/8/24 chris scott kra...@googlemail.com 2009/8/24 Maxim Khitrov mkhit...@gmail.com Hello all, I'm setting up a firewall using FreeBSD 7.2 and thought that it may not be a bad idea to have a continuous backup for important files like pf and dnsmasq configurations. By continuous I mean some script that would be triggered every few minutes from cron to automatically create a backup of any monitored file if it was modified. I also have a full system backup in place that is executed daily (dump/restore to a compact flash card), so the continuous backup would really be for times when someone makes a mistake editing one of the config files and needs to revert it to a previous state. My initial thought was to create a mercurial repository at the file system root and exclude everything except for explicitly added files. I'd then run something like hg commit -m `date` from cron every 10 minutes to record the changes automatically. Can anyone think of a better way to do this (existing port specifically for this purpose)? Obviously, I need a way to track the history of a file and revert to a previous state quickly. The storage of changes should be as size-efficient as possible. - Max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I rsync all my system files to a filer running zfs. I have a separate zfs fs for every host and then I snapshot the fs after the rsync. We then keep 35 snapshots for retention as we do daily rsyncs. You might want more of a rolling snapshot policy. Keep on for every 10 mins of the last hour, then drop it to hourly for the next 6 hours, then daily, then weekly etc Works quite well. We have also found it handy for forensics as well, when we have had a fault i forgot to say it need not be a zfs backend just a fs that you can reliably do snapshots ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Punkbuster
Jeff Molofee wrote: Can anyone tell me how to update punkbuster ... seems pbweb.x86 doesn't work anymore (302 errors) and I'm unable to run pbsetup.run it gives me a float point error, even after unpacking it with upx -d Specifically for enemy territory. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Have a look at http://linux-bsd-sharing.blogspot.com/2009/05/howto-enemy-territory-on-freebsd.html. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: moving a disk
On Mon, Aug 24, 2009 at 11:50:28AM -0400, PJ wrote: PJ wrote: I am trying to move a 7.2 installation to another computer where it is to be the only OS acting as a server for the lan. On bootup I get the message: Using drive 0, partition 3. And there it hangs. Probably because the boot code can't find the 3rd stage loader... It is strange that it is trying partition 3 instead of partition 4. Did you prepare the disk as explained in the handbook (§16.3 Adding Disks)? I get the impression that you didn't. And that can have caused the problem. Try booting again, and press any key to interrupt the boot process to get to the boot prompt. You should see something like: FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: At this boot prompt, type 0:ad(0,4,a)/boot/loaderENTER This will try to boot from the 4th partition. See boot(8). N.B. the boot manpage uses the term 'slice' for partitions. By default the boot code looks for either the active slice or the first slice with the freebsd type. I have tried to rewrite the mbr but that did absolutely nothing. That is not surprising, The mbr is only part of the boot process. The problem seems to be that it cannot locate the rest... Read the chapter The FreeBSD Booting Process from the FreeBSD Handbook. And see http://en.wikipedia.org/wiki/Master_boot_record This will provide insight into how FreeBSD actually boots. It is a bit of a convoluted process due to historical restrictions of the PC architecture. Reading the manual pages for fdisk(8), boot(8) and loader(8) might also prove enlightening. fik ad0 returns: partitions 1,2,3 are UNUSED Parrtition 4 give the cylinder, heads, sectors, blocks stuff Why did you install on partition 4? Normally one would use parition 1. What should I do? And what information do I need to supply or look for to solve this. See below. I'd rathernot go through another installation even if this is farly elementary. With any luck you don't have to. Oh, yes... all my former problems were definitely software related as I have checked and double, triple checked my HDDs and cannot find any problems therewith. here is what I have found in looking at the disk when it's mounted on another FBSD system through an USB interface: it is mounted on /dev/ad0 fdisk ad0 --- returns partitions 1,2,3 as UNUSED; partition 4 is marked for sysid 166 OpenBSD (this seems to be left over from an installation that was never completed) It should be type 165 for FreeBSD! _Or_ partition 4 should be marked as active (flag 80). Is it? If not you can use the -a flag of fdisk to update the active partition. I think you should use something like 'fdisk -u -a -4 ad0'. Look at the fdisk manual page to see what this does. I'm not sure if this is the right invocation. I have never dealt with this problem. Setting the active partition _should_ be enough. If that doesn't work, you're in trouble. As far as I know there is no easy way to just change the partition type, without starting over. In theory you can set the type by fiddling some bits in the partition table, but that is probably harder than it sounds. Maybe sysinstall can do it, but I haven't tried. Next time you want to install FreeBSD on a disk, read §16.3 Adding Disks of the FreeBSD handbook first, and follow the steps laid out there! That would create and active a single partition which would almost certainly have avoided this problem. I also note that the other functioning FBSD 7.2 has partitions 2-4 as UNUSED and partition 1 has the cylinder parameters. I get the impression that I should use the disklabel editor to change all that but am not familiar with it and am not sure how to use it. No. The disklabel works at a lower level. Historically PC harddisks can be divided into 4 partitions (This is what fdisk does). So the disk ad0 can have partitions 1--4: ad0s1--ad0s4. In older FreeBSD literature these are called slices, hence the 's' in the partition name. FreeBSD can subdivide a partition in labeled sections. These sections are labeled with a letter, so partition ad0s1 can be divided (in 7.x) into labeled pieces a--g: ad0s1a--ad0s1g. This is what the bsdlabel(8) program does. And it is usually on these subdivisions that filesystems are created with newfs(8). Is there a way to fix this thingy? Make sure that partition 4 is the active partition. That should fix it. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpi0YwFf2svf.pgp Description: PGP signature
Re: Continuous backup of critical system files
Maxim Khitrov wrote: I'm setting up a firewall using FreeBSD 7.2 and thought that it may not be a bad idea to have a continuous backup for important files like pf and dnsmasq configurations. By continuous I mean some script that would be triggered every few minutes from cron to automatically create a backup of any monitored file if it was modified. ... so the continuous backup would really be for times when someone makes a mistake editing one of the config files and needs to revert it to a previous state. It appears to me that you review your procedures rather than deploying such a backup solution. Critical files rarely change (or should rarely be modified), there should be no need to backup every 10 minutes. The more critical the file and the change applied the more testing should be done beforehand and the more care should be taken during the process to ensure that the original can easily be reinstated. You don't want to spend time digging it up from some backup. If your files are very critical then you should have a cvs repository in place as well as a testing environment. I guess this is not the case. If they are less critical then good practices are the way to go: Before modifying anything create a backup in the same location, I add a serial number rather than .bak, .old, .tmp, .new etc which is really confusing. I use, .MMDDXX, and .orig for the original/default file. It's easy to see when a file was modified and make diffs with the original and also delete old backups this way, with .old you really have no continuity, you can't name your next backup .older. Further, for small tweaks, I comment/uncomment parameters and apply these for fast testing from another session, so I don't even exit the editor. Certainly, I may save and test the file multiple times while tweaking, but in the end, there are only two files worth keeping: the last stable and the current. Of course, I'm not saying it's a bad idea to keep backups, only that if you find a need to continuously backup files as mentioned, then you should review your procedures. See also the current thread on what should be backed up. BR, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: moving a disk
Roland Smith wrote: On Mon, Aug 24, 2009 at 11:50:28AM -0400, PJ wrote: PJ wrote: I am trying to move a 7.2 installation to another computer where it is to be the only OS acting as a server for the lan. On bootup I get the message: Using drive 0, partition 3. And there it hangs. Probably because the boot code can't find the 3rd stage loader... It is strange that it is trying partition 3 instead of partition 4. Did you prepare the disk as explained in the handbook (�16.3 Adding Disks)? I get the impression that you didn't. And that can have caused the problem. Try booting again, and press any key to interrupt the boot process to get to the boot prompt. You should see something like: FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: At this boot prompt, type 0:ad(0,4,a)/boot/loaderENTER This will try to boot from the 4th partition. See boot(8). N.B. the boot manpage uses the term 'slice' for partitions. By default the boot code looks for either the active slice or the first slice with the freebsd type. I have tried to rewrite the mbr but that did absolutely nothing. That is not surprising, The mbr is only part of the boot process. The problem seems to be that it cannot locate the rest... Read the chapter The FreeBSD Booting Process from the FreeBSD Handbook. And see http://en.wikipedia.org/wiki/Master_boot_record This will provide insight into how FreeBSD actually boots. It is a bit of a convoluted process due to historical restrictions of the PC architecture. Reading the manual pages for fdisk(8), boot(8) and loader(8) might also prove enlightening. fik ad0 returns: partitions 1,2,3 are UNUSED Parrtition 4 give the cylinder, heads, sectors, blocks stuff Why did you install on partition 4? Normally one would use parition 1. What should I do? And what information do I need to supply or look for to solve this. See below. I'd rathernot go through another installation even if this is farly elementary. With any luck you don't have to. Oh, yes... all my former problems were definitely software related as I have checked and double, triple checked my HDDs and cannot find any problems therewith. here is what I have found in looking at the disk when it's mounted on another FBSD system through an USB interface: it is mounted on /dev/ad0 fdisk ad0 --- returns partitions 1,2,3 as UNUSED; partition 4 is marked for sysid 166 OpenBSD (this seems to be left over from an installation that was never completed) It should be type 165 for FreeBSD! _Or_ partition 4 should be marked as active (flag 80). Is it? If not you can use the -a flag of fdisk to update the active partition. I think you should use something like 'fdisk -u -a -4 ad0'. Look at the fdisk manual page to see what this does. I'm not sure if this is the right invocation. I have never dealt with this problem. Setting the active partition _should_ be enough. If that doesn't work, you're in trouble. As far as I know there is no easy way to just change the partition type, without starting over. In theory you can set the type by fiddling some bits in the partition table, but that is probably harder than it sounds. Maybe sysinstall can do it, but I haven't tried. Next time you want to install FreeBSD on a disk, read �16.3 Adding Disks of the FreeBSD handbook first, and follow the steps laid out there! That would create and active a single partition which would almost certainly have avoided this problem. I also note that the other functioning FBSD 7.2 has partitions 2-4 as UNUSED and partition 1 has the cylinder parameters. I get the impression that I should use the disklabel editor to change all that but am not familiar with it and am not sure how to use it. No. The disklabel works at a lower level. Historically PC harddisks can be divided into 4 partitions (This is what fdisk does). So the disk ad0 can have partitions 1--4: ad0s1--ad0s4. In older FreeBSD literature these are called slices, hence the 's' in the partition name. FreeBSD can subdivide a partition in labeled sections. These sections are labeled with a letter, so partition ad0s1 can be divided (in 7.x) into labeled pieces a--g: ad0s1a--ad0s1g. This is what the bsdlabel(8) program does. And it is usually on these subdivisions that filesystems are created with newfs(8). Is there a way to fix this thingy? Make sure that partition 4 is the active partition. That should fix it. Hi Roland, I'm going to keep this email as a valued reminder of what to do and not to do. I'm afraid I was a bit impatient and messed up the already messed up disk... frankly, I don't recall whatever happened to the thing in the first place. I did install a good working 7.2 with samba, mysawl, php and that's about it. It booted fine and I just left it alone not being sure of what I would do with
Re: moving a disk
On 8/24/09, Roland Smith rsm...@xs4all.nl wrote: On Mon, Aug 24, 2009 at 11:50:28AM -0400, PJ wrote: PJ wrote: I am trying to move a 7.2 installation to another computer where it is to be the only OS acting as a server for the lan. On bootup I get the message: Using drive 0, partition 3. And there it hangs. Probably because the boot code can't find the 3rd stage loader... It is strange that it is trying partition 3 instead of partition 4. 0-based. OpenBSD when set to install and use all of a disk, sets it to the last primary partition (1-based = 4, 0-based = 3). Did you prepare the disk as explained in the handbook (§16.3 Adding Disks)? I get the impression that you didn't. And that can have caused the problem. Try booting again, and press any key to interrupt the boot process to get to the boot prompt. You should see something like: FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: At this boot prompt, type 0:ad(0,4,a)/boot/loaderENTER This will try to boot from the 4th partition. See boot(8). N.B. the boot manpage uses the term 'slice' for partitions. By default the boot code looks for either the active slice or the first slice with the freebsd type. This drive still is likely having OpenBSD bootblocks in the MBR and track. I don't expect OpenBSD to boot FreeBSD. I have tried to rewrite the mbr but that did absolutely nothing. That is not surprising, The mbr is only part of the boot process. The problem seems to be that it cannot locate the rest... Read the chapter The FreeBSD Booting Process from the FreeBSD Handbook. And see http://en.wikipedia.org/wiki/Master_boot_record This will provide insight into how FreeBSD actually boots. It is a bit of a convoluted process due to historical restrictions of the PC architecture. Reading the manual pages for fdisk(8), boot(8) and loader(8) might also prove enlightening. fik ad0 returns: partitions 1,2,3 are UNUSED Parrtition 4 give the cylinder, heads, sectors, blocks stuff Why did you install on partition 4? Normally one would use parition 1. and sysinstall would use (0-based = 0, 1-based = 1) the first partition too. What should I do? And what information do I need to supply or look for to solve this. See below. I'd rathernot go through another installation even if this is farly elementary. With any luck you don't have to. Oh, yes... all my former problems were definitely software related as I have checked and double, triple checked my HDDs and cannot find any problems therewith. here is what I have found in looking at the disk when it's mounted on another FBSD system through an USB interface: it is mounted on /dev/ad0 fdisk ad0 --- returns partitions 1,2,3 as UNUSED; partition 4 is marked for sysid 166 OpenBSD (this seems to be left over from an installation that was never completed) It should be type 165 for FreeBSD! _Or_ partition 4 should be marked as active (flag 80). Is it? If not you can use the -a flag of fdisk to update the active partition. I think you should use something like 'fdisk -u -a -4 ad0'. Look at the fdisk manual page to see what this does. I'm not sure if this is the right invocation. I have never dealt with this problem. Setting the active partition _should_ be enough. If that doesn't work, you're in trouble. As far as I know there is no easy way to just change the partition type, without starting over. In theory you can set the type by fiddling some bits in the partition table, but that is probably harder than it sounds. Maybe sysinstall can do it, but I haven't tried. Next time you want to install FreeBSD on a disk, read §16.3 Adding Disks of the FreeBSD handbook first, and follow the steps laid out there! That would create and active a single partition which would almost certainly have avoided this problem. I also note that the other functioning FBSD 7.2 has partitions 2-4 as UNUSED and partition 1 has the cylinder parameters. I get the impression that I should use the disklabel editor to change all that but am not familiar with it and am not sure how to use it. No. The disklabel works at a lower level. Historically PC harddisks can be divided into 4 partitions (This is what fdisk does). So the disk ad0 can have partitions 1--4: ad0s1--ad0s4. In older FreeBSD literature these are called slices, hence the 's' in the partition name. FreeBSD can subdivide a partition in labeled sections. These sections are labeled with a letter, so partition ad0s1 can be divided (in 7.x) into labeled pieces a--g: ad0s1a--ad0s1g. This is what the bsdlabel(8) program does. And it is usually on these subdivisions that filesystems are created with newfs(8). Is there a way to fix this thingy? Make sure that partition 4 is the active partition. That should fix it. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed
Equivilant of 'lsmod'
What is the equivalent of the Linux 'lsmod' command in FreeBSD? -- Jerry ges...@yahoo.com To be or not to be, that is the bottom line. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Equivilant of 'lsmod'
On Mon, Aug 24, 2009 at 2:29 PM, Jerryges...@yahoo.com wrote: What is the equivalent of the Linux 'lsmod' command in FreeBSD? -- Jerry ges...@yahoo.com I think it's kldstat. Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
hard disk failure - now what?
I just experienced a hard drive failure on one of my FreeBSD 7.2 production servers with no backup! I am so mad at myself for not backing up!! Now it's a salvage operation. Here are the type of errors I was getting on the console, over-and-over: ad4: TIMEOUT - WRITE_DMA48 retrying (0 retries left) LBA=441633503 ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly ad4: FAILURE - WRITE_DMA48 timed out LBA=441633375 g_vgs_done():ad4s1f[WRITE(offset=216338284544, length=16384)]error = 5 I could still login to the machine (after an eternity) but got lots of read/write errors along the way. The offset shown in the errors kept changing, so I thought it was a hardware eSATA controller issue instead of a bad sector on the drive - I replaced the motherboard, but the problem persisted. So I bought a new hard drive and have re-installed FreeBSD 7.2 on it. I'd like to plug in the old hard drive today, mount it and salvage as much as I can... especially the database files, config files, etc. My question: what kind of checks and/or repair tools should I run on the damaged drive after it's mounted? Or should I mount it as read-only and start backing it up? I am hoping most of my data is still there, but also don't want to damage it further. I desperately need to salvage the data, what do the kind people on this list recommend? thanks, kelly ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Equivilant of 'lsmod'
In the last episode (Aug 24), Jerry said: What is the equivalent of the Linux 'lsmod' command in FreeBSD? Remember to actually describe what you want, rather than just giving the linux command. To list the loaded kernel modules, run kldstat. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Equivilant of 'lsmod'
Dan Nelson wrote: In the last episode (Aug 24), Jerry said: What is the equivalent of the Linux 'lsmod' command in FreeBSD? Remember to actually describe what you want, rather than just giving the linux command. To list the loaded kernel modules, run kldstat. I think he wanted to know what the equivalent of the Linux 'lsmod' command is. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Equivilant of 'lsmod'
I believe it would be 'kldstat' On Mon, Aug 24, 2009 at 08:44:38PM +0100, Dunc thus spake: Dan Nelson wrote: In the last episode (Aug 24), Jerry said: What is the equivalent of the Linux 'lsmod' command in FreeBSD? Remember to actually describe what you want, rather than just giving the linux command. To list the loaded kernel modules, run kldstat. I think he wanted to know what the equivalent of the Linux 'lsmod' command is. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Equivilant of 'lsmod'
On Mon, 24 Aug 2009 14:33:09 -0500 Dan Nelson dnel...@allantgroup.com wrote: In the last episode (Aug 24), Jerry said: What is the equivalent of the Linux 'lsmod' command in FreeBSD? Remember to actually describe what you want, rather than just giving the linux command. To list the loaded kernel modules, run kldstat. I was looking for something like this snippet from a Linux machine and using lsmod: Module Size Used by af_packet 34440 2 ppdev 18568 0 acpi_cpufreq 18448 3 cpufreq_stats 16032 0 cpufreq_powersave 10368 0 cpufreq_ondemand 18320 2 freq_table 14080 3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand cpufreq_userspace 14468 0 cpufreq_conservative17800 0 iptable_filter 11776 0 ip_tables 31720 1 iptable_filter x_tables 30728 1 ip_tables ac 15496 0 parport_pc 48296 0 lp 22084 0 parport51340 3 ppdev,parport_pc,lp loop 28676 0 nfs 298872 1 lockd 83248 2 nfs nfs_acl12416 1 nfs sunrpc220808 10 nfs,lockd,nfs_acl container 13824 0 iTCO_wdt 22480 0 button 18080 0 pcspkr 12160 0 evdev 22144 3 iTCO_vendor_support12932 1 iTCO_wdt shpchp 45340 0 pci_hotplug41776 1 shpchp ext3 156176 7 jbd64168 1 ext3 mbcache18560 1 ext3 sg 48920 0 sr_mod 27300 0 cdrom 48680 1 sr_mod sd_mod 40448 12 pata_acpi 17024 0 usbhid 42848 0 hid52160 1 usbhid ata_piix 31364 10 ata_generic17156 0 libata183984 3 pata_acpi,ata_piix,ata_generic ehci_hcd 49164 0 scsi_mod 185784 4 sg,sr_mod,sd_mod,libata tg3 131972 0 uhci_hcd 37024 0 usbcore 177200 4 usbhid,ehci_hcd,uhci_hcd raid10 33536 0 raid456 138272 0 async_xor 13312 1 raid456 async_memcpy 11776 1 raid456 async_tx 17652 3 raid456,async_xor,async_memcpy xor14352 2 raid456,async_xor raid1 33920 5 raid0 16640 0 multipath 18176 0 linear 14592 0 md_mod 95388 11 raid10,raid456,raid1,raid0,multipath,linear dm_mirror 33408 0 dm_snapshot27848 0 dm_mod 78200 11 dm_mirror,dm_snapshot thermal26912 0 processor 48712 2 acpi_cpufreq,thermal fan13960 0 fbcon 53504 0 tileblit 11392 1 fbcon font 17280 1 fbcon bitblit14592 1 fbcon softcursor 10880 1 bitblit fuse 63280 1 -- Jerry ges...@yahoo.com A man was reading The Canterbury Tales one Saturday morning, when his wife asked What have you got there? Replied he, Just my cup and Chaucer. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: hard disk failure - now what?
On 8/24/09, Kelly Martin kellymar...@gmail.com wrote: I just experienced a hard drive failure on one of my FreeBSD 7.2 production servers with no backup! I am so mad at myself for not backing up!! Now it's a salvage operation. Here are the type of errors I was getting on the console, over-and-over: ad4: TIMEOUT - WRITE_DMA48 retrying (0 retries left) LBA=441633503 ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly ad4: FAILURE - WRITE_DMA48 timed out LBA=441633375 g_vgs_done():ad4s1f[WRITE(offset=216338284544, length=16384)]error = 5 I could still login to the machine (after an eternity) but got lots of read/write errors along the way. The offset shown in the errors kept changing, so I thought it was a hardware eSATA controller issue instead of a bad sector on the drive - I replaced the motherboard, but the problem persisted. So I bought a new hard drive and have re-installed FreeBSD 7.2 on it. I'd like to plug in the old hard drive today, mount it and salvage as much as I can... especially the database files, config files, etc. My question: what kind of checks and/or repair tools should I run on the damaged drive after it's mounted? Or should I mount it as read-only and start backing it up? I am hoping most of my data is still there, but also don't want to damage it further. I desperately need to salvage the data, what do the kind people on this list recommend? thanks, kelly If I were you, get a copy of spinrite (from grc.com) and always keep it handy. It can be risky on a drive already failing. Here's what I'd do Buy spinrite, no matter what. slave the bad drive, read-only mount.. even if the FS is dirty, read-only.. no fsck. copy the data you can (if any). reboot and run spinrite on the bad drive, deepest analysis (level 4 or 5) [may take days, weeks or even reports of months] re-slave the bad drive to the system, fsck and mount read-only. compare and copy any additional data, if any/if applicable, you can. Scrap/destroy the drive if it has sensitive data. I crack open the drive and dismantle the HDD platters from the spindle, break the read-write head ribbon cable, and remove the circuit board on the drive when I destroy drives. Each component should be recycled (being the responsible citizen), maybe on separate runs to remove the possibility of someone nosy getting into your stuff. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: hard disk failure - now what?
Kelly Martin kellymar...@gmail.com writes: I just experienced a hard drive failure on one of my FreeBSD 7.2 production servers with no backup! I am so mad at myself for not backing up!! Now it's a salvage operation. Here are the type of errors I was getting on the console, over-and-over: ad4: TIMEOUT - WRITE_DMA48 retrying (0 retries left) LBA=441633503 ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly ad4: FAILURE - WRITE_DMA48 timed out LBA=441633375 g_vgs_done():ad4s1f[WRITE(offset=216338284544, length=16384)]error = 5 I could still login to the machine (after an eternity) but got lots of read/write errors along the way. The offset shown in the errors kept changing, so I thought it was a hardware eSATA controller issue instead of a bad sector on the drive - I replaced the motherboard, but the problem persisted. So I bought a new hard drive and have re-installed FreeBSD 7.2 on it. I'd like to plug in the old hard drive today, mount it and salvage as much as I can... especially the database files, config files, etc. My question: what kind of checks and/or repair tools should I run on the damaged drive after it's mounted? Or should I mount it as read-only and start backing it up? I am hoping most of my data is still there, but also don't want to damage it further. I desperately need to salvage the data, what do the kind people on this list recommend? First, try copying the entire disk, *without* mounting it. Use dd(1) to get a copy of the whole disk. I believe that conv=noerror may be necessary. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: hard disk failure - now what?
On Mon, 24 Aug 2009 12:29:19 -0600, Kelly Martin kellymar...@gmail.com wrote: My question: what kind of checks and/or repair tools should I run on the damaged drive after it's mounted? Or should I mount it as read-only and start backing it up? Thou shalt not manipluate thy file systems while they are mounted. :-) Perform an fsck on the partitions first, then mount them ro. Copy the files you need. In case you can't reach essential files, you have the change to use forensic tools to get them. Finally, keep in mind that for further diagnostics and restore operations it's always wise not to use the original file systems, i. e. the original disk. Make dd copies of the partitions onto a working disk and use them instead. Luckily, most operations work on plain files as well as on block device specials. I am hoping most of my data is still there, but also don't want to damage it further. Good idea. This encourages you to follow the advice given above. I desperately need to salvage the data, what do the kind people on this list recommend? BACKUPS!!! =^_^= -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: hard disk failure - now what?
On Mon, 24 Aug 2009 14:13:22 -0600, Tim Judd taj...@gmail.com wrote: If I were you, get a copy of spinrite (from grc.com) and always keep it handy. It can be risky on a drive already failing. Here's what I'd do Buy spinrite, no matter what. Is it really such a good tool? From my own problems, I researched that common recovery tools are R-Studio and UFS Explorer. Both do not natively run on BSD, but the first one offers a bootable CD. Without buying, you can run the diagnostics mode fullwise. For recovery, you need to buy the program. The Spinrite web page reads as follows: The industry's #1 hard drive data recovery software is NOW COMPATIBLE with NTFS, FAT, Linux, and ALL OTHER file systems! What? Linux and other file systems? Is this just marketing, in order to look good to the not very educated ones? Or do they not know what they're talking about? In fact, I will keep an eye on this program. Maybe it can help me get my data back (inode defect of $HOME entry). I'm reading their web page some more right now. slave the bad drive, read-only mount.. even if the FS is dirty, read-only.. no fsck. You can at least do one fsck run without any modification options, like a read only file system check. This of course can - like any read operation on the disk - be risky if the disk is fast degrading, simply by using it. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Newbie discovers two useful apps...
Even after a year or so of administering a number of FreeBSD servers, I still consider myself to be a newbie (see my various posts for evidence of this fact!) I've been hoping to have something useful to contribute back, and I suddenly realized there are probably newbies that are even newbier than I. Hard to believe, but true! You pros can flip to the next post, there's nothing here for you, but my fellow newbies may find this interesting... Anyway, this weekend I 'discovered' two VERY useful utilities: 1. The 'at' command: http://tinyurl.com/nzz5a9 I don't know about you, but I am constantly promising clients that something will happen at an odd hour of the day or night. A typical example is someone who wants some promotion to end at 7:30 am. Accomplishing this is pretty simple, but has required me to log into the server to manually execute some command, or write some tiny script and have it execute by cron in some tortured way. Super inconvenient, or a waste of time, or worse (if you forget). But this weekend I discovered the 'at' command. The man page gives you the details, but basically it allows you to say execute that command or set of commands at this time on this day. You can set up the 'at' command to do what you need to do at 2am on Tuesday and forget it. No more setting alarms or forgetting. And it's dead easy to set up. I can't believe I haven't found this sooner. Fantastic. 2. DJB Daemontools: http://thedjbway.org/daemontools.html Lots of programs that are meant to run as daemons come packaged with a nice rc.d script. You just configure them in /etc/rc.d and they come up automatically when you reboot. But not all, and frankly I have never had time to figure out how to write a rc.d script. I really, really needed to get a linux-oriented daemon to work this weekend -- rubycas-server, if you are interested. But it doesn't have an rc.d script. Bummer. However, I run tinydns as my dns server, and that program doesn't use rc.d scripts, either. DJB has his own way of doing things, apparently. The standard way to install tinydns has you install another DJB product called daemontools. Daemontools is good for, well, getting daemons to run at boot time, in a fairly platform independent way (UNIX only, of course). Anyway, I dimly remembered this and dug into the DJB docs. Some will wonder why I found it easier to read a DJB doc than to read how to write a rc.d script... An excellent question, but in 5 minutes, I had my rubycas-server running under daemontools. It is that easy. I still don't know how to write an rc.d script, but I have to believe it would take me more than 5 minutes to learn and write. If you have daemons running, that you started manually from the command line, and are just hoping you'll remember to re-start them the next time you reboot, you should really check out daemontools... Much better than putting a reminder in your MOD (Me??? I would never do that!!!) -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: hard disk failure - now what?
On 8/24/09, Polytropon free...@edvax.de wrote: On Mon, 24 Aug 2009 14:13:22 -0600, Tim Judd taj...@gmail.com wrote: If I were you, get a copy of spinrite (from grc.com) and always keep it handy. It can be risky on a drive already failing. Here's what I'd do Buy spinrite, no matter what. Is it really such a good tool? From my own problems, I researched that common recovery tools are R-Studio and UFS Explorer. Both do not natively run on BSD, but the first one offers a bootable CD. Without buying, you can run the diagnostics mode fullwise. For recovery, you need to buy the program. The Spinrite web page reads as follows: The industry's #1 hard drive data recovery software is NOW COMPATIBLE with NTFS, FAT, Linux, and ALL OTHER file systems! It's OS/FS independent. it works on the bits stored on the magnetic platters, NOT on a filesystem. TiVo, Linux, BSD and Mac OSX drives are treated the same. Bits on a magnetic platter. It's recovery stems from the randomization and movement of the head to the sector in question that allows it to salvage any bits it can (for example, other recovery will abandon 512bytes if 1 bit cannot be read. spinrite will recover 512bytes-1bit to a hard drive's spare sector once spinrite says i'm done working with this sector.) It leads to a very successful rate. What? Linux and other file systems? Is this just marketing, in order to look good to the not very educated ones? Or do they not know what they're talking about? In fact, I will keep an eye on this program. Maybe it can help me get my data back (inode defect of $HOME entry). I'm reading their web page some more right now. Again, works on the bits. if it's a bit problem, it will do it's best to fix the problem, unless it's a hardware defect and cannot be relocated. If enough sectors are relocated, and the drive has run out of spare sectors, it's time to scrap the drive anyway. slave the bad drive, read-only mount.. even if the FS is dirty, read-only.. no fsck. You can at least do one fsck run without any modification options, like a read only file system check. This of course can - like any read operation on the disk - be risky if the disk is fast degrading, simply by using it. which is why i recommend against making changes to the disk until a spinrite has completed. Personally, I setup a spinrite to be net-bootable (not officially supported). I can write a walkthrough to people who want to net-boot it. I won't provide spinrite, of course. I currently netboot: FreeBSD memtest86 spinrite with no changes to my setup any time I want to boot anything. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problem mounting EXT2FS
Hi folks, im migrating from Linux to BSD, and i found my first problem... First of all, i did save my /home from my old Linux distribution on another HD, ext2fs partition /dev/ad6s1... I can correctly see the drive from sysinstall. I read about compiling the KERNEL in order to add Ext2fs support under Freebsd, wich I did... Adding the line: Quote: options EXT2FS looking like this: Quote: options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. options STOP_NMI # Stop CPUS using NMI instead of IPI options AUDIT # Security event auditing #options KDTRACE_FRAME # Ensure frames are compiled in *options EXT2FS* #options KDTRACE_HOOKS # Kernel DTrace hooks After this i recompiled the kernel and installed... Quote: # uname -a FreeBSD 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Mon Aug 24 18:59:43 UTC 2009 iscariote@:/usr/obj/usr/src/sys/MYKERNEL amd64 Well... everything should be ready now to mount my ext2fs partition... Using the following command... Quote: # mount /dev/ad8s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad8s1e on /tmp (ufs, local, soft-updates) /dev/ad8s1f on /usr (ufs, local, soft-updates) /dev/ad8s1d on /var (ufs, local, soft-updates) /dev/ntfs/DATOSWIN on /media/DATOSWIN (ntfs, local, nosuid) # mount -t extfs2 /dev/ad6s1 /ext2 mount: /dev/ad6s1 : Operation not supported by device I tried several times, with not luck, one of those times i was able to mount it, but not to access it, when i tried to cd /ext2 (folder when is mounted) system tells me that ext2 is not a folder... any ideas??? Thanks in advance!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Equivilant of 'lsmod'
On Mon 24 Aug 2009 at 12:44:38 PDT Dunc wrote: Dan Nelson wrote: In the last episode (Aug 24), Jerry said: What is the equivalent of the Linux 'lsmod' command in FreeBSD? Remember to actually describe what you want, rather than just giving the linux command. To list the loaded kernel modules, run kldstat. I think he wanted to know what the equivalent of the Linux 'lsmod' command is. Is kldstat 100% semantically congruent with lsmod? I.e., are there things you can do with lsmod that you can't with kldstat? A quick comparison of the manpages will probably give the answer, but it will save everyone some time if the OP explains what he wants to do that he would have used lsmod for if this were Linux. Besides, not everyone here is familiar with Linux and not everyone wants to spend any time learning it. Just giving the Linux command for something means you're unnecessarily narrowing down the number of people who can give you an answer. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem mounting EXT2FS
Judging by your uname output, the #0 should be #1 if it's reading a re- compiled kernel. I would double check that you used the proper KERNCONF for make buildkernel and make installkernel. For example, I recompiled my kernel and note the output: [r...@arthur /var/account]# uname -a FreeBSD arthur.silvertree.org 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #1: Fri Aug 14 13:27:47 PDT 2009 r...@arthur.silvertree.org:/usr/ obj/usr/src/sys/ARTHUR i386 See the #1? That shows me that the kernel has been recompiled once. The fact it says MYKERNEL for the kernel config, make sure that you copied GENERIC to MYKERNEL in /usr/src/sys/i386/conf/ I used the handbook and actually put ARTHUR in /root/kernels and in / usr/src/sys/i386/conf: [r...@arthur ~/kernels]# ls -la /usr/src/sys/i386/conf/ARTHUR lrwxr-xr-x 1 root wheel 20 Jul 29 07:57 /usr/src/sys/i386/conf/ ARTHUR - /root/kernels/ARTHUR I'd suggest that you didn't compile the right kernel config file. Another suggestion I used was to add in /etc/make.conf: KERNCONF=ARTHUR So add KERNCONF=MYKERNEL then copy /usr/src/sys/i386/conf/GENERIC to /usr/src/sys/i386/conf/MYKERNEL then edit MYKERNEL as needed and with that line in /etc/make.conf: cd /usr/src make buildkernel make installkernel shutdown -r now I may be off base, but I'd start with double checking the kernel config file used for buildkernel and installkernel. Scott On Aug 24, 2009, at 13:20:29, Jeronimo Calvo wrote: Hi folks, im migrating from Linux to BSD, and i found my first problem... First of all, i did save my /home from my old Linux distribution on another HD, ext2fs partition /dev/ad6s1... I can correctly see the drive from sysinstall. I read about compiling the KERNEL in order to add Ext2fs support under Freebsd, wich I did... Adding the line: Quote: options EXT2FS looking like this: Quote: options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. options STOP_NMI # Stop CPUS using NMI instead of IPI options AUDIT # Security event auditing #options KDTRACE_FRAME # Ensure frames are compiled in *options EXT2FS* #options KDTRACE_HOOKS # Kernel DTrace hooks After this i recompiled the kernel and installed... Quote: # uname -a FreeBSD 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Mon Aug 24 18:59:43 UTC 2009 iscariote@:/usr/obj/usr/src/sys/MYKERNEL amd64 Well... everything should be ready now to mount my ext2fs partition... Using the following command... Quote: # mount /dev/ad8s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad8s1e on /tmp (ufs, local, soft-updates) /dev/ad8s1f on /usr (ufs, local, soft-updates) /dev/ad8s1d on /var (ufs, local, soft-updates) /dev/ntfs/DATOSWIN on /media/DATOSWIN (ntfs, local, nosuid) # mount -t extfs2 /dev/ad6s1 /ext2 mount: /dev/ad6s1 : Operation not supported by device I tried several times, with not luck, one of those times i was able to mount it, but not to access it, when i tried to cd /ext2 (folder when is mounted) system tells me that ext2 is not a folder... any ideas??? Thanks in advance!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem mounting EXT2FS
Maybe just malquoted, but... On Mon, 24 Aug 2009 20:20:29 +, Jeronimo Calvo jeronimocal...@googlemail.com wrote: # mount -t extfs2 /dev/ad6s1 /ext2 mount: /dev/ad6s1 : Operation not supported by device The command should include -t ext2fs, not extfs2, as far as I remember. I haven't run Linux for almost 10 years now... I tried several times, with not luck, one of those times i was able to mount it, but not to access it, when i tried to cd /ext2 (folder when is mounted) system tells me that ext2 is not a folder... There are no folders in the UNIX file system hierarchy. The things you're mentioning are called directories. I know, that's just terminology, but it's important to use the correct words context-wise. You don't call the files sheets of paper, do you? :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: hard disk failure - now what?
On Mon, 24 Aug 2009 14:51:41 -0600, Tim Judd taj...@gmail.com wrote: It's OS/FS independent. it works on the bits stored on the magnetic platters, NOT on a filesystem. Ah, I see. So it's primarily intended for diagnosing and recovering from physically defective disks. Good to know, because there are times when you exactly need to do this. So it's much more hardware oriented than the usual candidates for recovery programs. So the strange mentioning of Linux and other file systems just seems to be of a marketing nature. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: hard disk failure - now what?
On 8/24/09, Polytropon free...@edvax.de wrote: On Mon, 24 Aug 2009 14:51:41 -0600, Tim Judd taj...@gmail.com wrote: It's OS/FS independent. it works on the bits stored on the magnetic platters, NOT on a filesystem. Ah, I see. So it's primarily intended for diagnosing and recovering from physically defective disks. Good to know, because there are times when you exactly need to do this. So it's much more hardware oriented than the usual candidates for recovery programs. So the strange mentioning of Linux and other file systems just seems to be of a marketing nature. :-) whatever you would like to call it, I find it accurate description of the product and it avoids false advertising. Not just diagnostics and recovery, it's for preventive maintenance, and healthy operations too. Most people who use it are in a diagnostics and recovery, but if you always use it as preventive maintenance, you'll never need to use it for diagnostics and recovery. People complain about it: I keep running spinrite, but it never finds problems! exactly, it's doing it's job and not having to recover. It's doing the work the drive needs to swap out bad sectors and everything. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: moving a disk
On Mon, Aug 24, 2009 at 02:33:25PM -0400, PJ wrote: I'm afraid I was a bit impatient Patience is a virtue. Installing stuff can take hours, and a split-second can suffice to screw it all up. Been there done that. :-) and messed up the already messed up disk... frankly, I don't recall whatever happened to the thing in the first place. Can I give you a tip? If you are doing something new or hairy, keep a laptop or even a paper notebook handy and make notes of what you do. Write down the commands that you use and any error messages that you get. My favorite technique is to open emacs (preferably on another machine), start a terminal/ssh session inside an emacs buffer and then do my thing. This gives me a complete record of what I've done. Save these session (with some added explanations) to a file and you'll know what to do next time, or at least you can explain to others what you've been doing. anyway, I'm just practicing another minimal install... it's not as bad as I had thought... I'm getting it all together now. There is an extremely easy way to get all ports that you need onto a new machine, provided that you have a (base) machine of (a) the same FreeBSD major version of (b) the same hardware architecture and (c) up-to-date installed ports available. On the base machine, make dump(8)s of the filesystem(s) containing /usr/local, /var/db/ports and /var/db/pkg and save them to files. Transfer those dump files to an external harddisk or DVD. Using restore(8) interactively on the new machine, restore these three directories to their respective filesystems and you've got all ports up and running save for some editing of /etc/rc.conf. Thanks much, I'm beginning to understand a bit more... this boot stuff sure is complicated... Yep. PC booting is a throwback to an earlier era when 640 kB RAM was all there was and 512 bytes seemed big enough for boot code, because you were writing in machine language or assembly anyway. If you want a real hair-raising story about the time that assemblers were luxuries, google 'the story of Mel' and be amazed (or horrified). It predates PCs, but I think it shows the mind-set of the begin time of (personal) computing. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp1sVY5UbbCi.pgp Description: PGP signature
Re: hard disk failure - now what?
On Mon, 24 Aug 2009 15:32:05 -0600, Tim Judd taj...@gmail.com wrote: Not just diagnostics and recovery, it's for preventive maintenance, and healthy operations too. Most people who use it are in a diagnostics and recovery, but if you always use it as preventive maintenance, you'll never need to use it for diagnostics and recovery. People complain about it: I keep running spinrite, but it never finds problems! exactly, it's doing it's job and not having to recover. It's doing the work the drive needs to swap out bad sectors and everything. Well, and its price is not as high as most recovery tools. So prevention is cheaper than intervention here. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem mounting EXT2FS
True you are right... I was using the incorrect syntax and the incorrect word hehehhe well I did try as well using the correct procedure: Thats the result (mounted but not accesible) [root@ /media/DATOSWIN]# mount /dev/ad8s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad8s1e on /tmp (ufs, local, soft-updates) /dev/ad8s1f on /usr (ufs, local, soft-updates) /dev/ad8s1d on /var (ufs, local, soft-updates) /dev/ntfs/DATOSWIN on /media/DATOSWIN (ntfs, local, nosuid) [root@ /media/DATOSWIN]# *mount -t ext2fs /dev/ad6s1 /ext2* [root@ /media/DATOSWIN]# cd /ext2 *bash: cd: /ext2: Not a directory* [root@ /media/DATOSWIN]# ls -la /ext2 *ls: /ext2: Bad file descriptor* [root@ /media/DATOSWIN]# 2009/8/24 Polytropon free...@edvax.de Maybe just malquoted, but... On Mon, 24 Aug 2009 20:20:29 +, Jeronimo Calvo jeronimocal...@googlemail.com wrote: # mount -t extfs2 /dev/ad6s1 /ext2 mount: /dev/ad6s1 : Operation not supported by device The command should include -t ext2fs, not extfs2, as far as I remember. I haven't run Linux for almost 10 years now... I tried several times, with not luck, one of those times i was able to mount it, but not to access it, when i tried to cd /ext2 (folder when is mounted) system tells me that ext2 is not a folder... There are no folders in the UNIX file system hierarchy. The things you're mentioning are called directories. I know, that's just terminology, but it's important to use the correct words context-wise. You don't call the files sheets of paper, do you? :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Continuous backup of critical system files
On Mon, Aug 24, 2009 at 11:57:25AM -0400, Maxim Khitrov wrote: Hello all, I'm setting up a firewall using FreeBSD 7.2 and thought that it may not be a bad idea to have a continuous backup for important files like pf and dnsmasq configurations. snip My initial thought was to create a mercurial repository at the file system root and exclude everything except for explicitly added files. I'd then run something like hg commit -m `date` from cron every 10 minutes to record the changes automatically. Isn't this ass-backwards? Configuration files shouldn't change suddenly. My system is to keep all configuration files that I have changed from their defaults in a revision control system repository. That is where I add and (after testing) commit changes to those files. I then use an install script to copy changed files (based on SHA1 checksum) to their correct location in /etc or /usr/local/etc and run restart commands if necessary. So installation is always done from the repository to the filesystem. If a change doesn't work I just check out the last good version of the file(s), re-run the install script and we're back to normal. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpNaMjPLXuPF.pgp Description: PGP signature
Re: Newbie discovers two useful apps...
--On Monday, August 24, 2009 15:45:16 -0500 John Almberg jalmb...@identry.com wrote: 2. DJB Daemontools: http://thedjbway.org/daemontools.html [snip] Anyway, I dimly remembered this and dug into the DJB docs. Some will wonder why I found it easier to read a DJB doc than to read how to write a rc.d script... An excellent question, but in 5 minutes, I had my rubycas-server running under daemontools. It is that easy. I still don't know how to write an rc.d script, but I have to believe it would take me more than 5 minutes to learn and write. If you have daemons running, that you started manually from the command line, and are just hoping you'll remember to re-start them the next time you reboot, you should really check out daemontools... Much better than putting a reminder in your MOD (Me??? I would never do that!!!) John, I have tried to convert linux startups scripts over to rc.d scripts for some of my ports. Frankly, it's easier to start from scratch. In some cases it's barely possible at all, especially when the software was written for Linux with no consideration at all for other unix platforms. This particular tip will save a lot of people a lot of grief, I can assure you. Thanks for sharing it. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
(solved) Re: Problem mounting EXT2FS
Thanks a lot fellas!! problem resolved!!! On 24/08/2009, Gonzalo Nemmi gne...@gmail.com wrote: On Monday 24 August 2009 6:44:24 pm Jeronimo Calvo wrote: True you are right... I was using the incorrect syntax and the incorrect word hehehhe well I did try as well using the correct procedure: Thats the result (mounted but not accesible) [root@ /media/DATOSWIN]# mount /dev/ad8s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad8s1e on /tmp (ufs, local, soft-updates) /dev/ad8s1f on /usr (ufs, local, soft-updates) /dev/ad8s1d on /var (ufs, local, soft-updates) /dev/ntfs/DATOSWIN on /media/DATOSWIN (ntfs, local, nosuid) [root@ /media/DATOSWIN]# *mount -t ext2fs /dev/ad6s1 /ext2* [root@ /media/DATOSWIN]# cd /ext2 *bash: cd: /ext2: Not a directory* [root@ /media/DATOSWIN]# ls -la /ext2 *ls: /ext2: Bad file descriptor* [root@ /media/DATOSWIN]# Here's the problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/124621 Here's how to solve it: http://forums.freebsd.org/showthread.php?t=912highlight=ext2fs 2009/8/24 Polytropon free...@edvax.de Maybe just malquoted, but... On Mon, 24 Aug 2009 20:20:29 +, Jeronimo Calvo jeronimocal...@googlemail.com wrote: # mount -t extfs2 /dev/ad6s1 /ext2 mount: /dev/ad6s1 : Operation not supported by device The command should include -t ext2fs, not extfs2, as far as I remember. I haven't run Linux for almost 10 years now... I tried several times, with not luck, one of those times i was able to mount it, but not to access it, when i tried to cd /ext2 (folder when is mounted) system tells me that ext2 is not a folder... There are no folders in the UNIX file system hierarchy. The things you're mentioning are called directories. I know, that's just terminology, but it's important to use the correct words context-wise. You don't call the files sheets of paper, do you? :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Blessings Gonzalo Nemmi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem mounting EXT2FS
On Monday 24 August 2009 6:44:24 pm Jeronimo Calvo wrote: True you are right... I was using the incorrect syntax and the incorrect word hehehhe well I did try as well using the correct procedure: Thats the result (mounted but not accesible) [root@ /media/DATOSWIN]# mount /dev/ad8s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad8s1e on /tmp (ufs, local, soft-updates) /dev/ad8s1f on /usr (ufs, local, soft-updates) /dev/ad8s1d on /var (ufs, local, soft-updates) /dev/ntfs/DATOSWIN on /media/DATOSWIN (ntfs, local, nosuid) [root@ /media/DATOSWIN]# *mount -t ext2fs /dev/ad6s1 /ext2* [root@ /media/DATOSWIN]# cd /ext2 *bash: cd: /ext2: Not a directory* [root@ /media/DATOSWIN]# ls -la /ext2 *ls: /ext2: Bad file descriptor* [root@ /media/DATOSWIN]# Here's the problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/124621 Here's how to solve it: http://forums.freebsd.org/showthread.php?t=912highlight=ext2fs 2009/8/24 Polytropon free...@edvax.de Maybe just malquoted, but... On Mon, 24 Aug 2009 20:20:29 +, Jeronimo Calvo jeronimocal...@googlemail.com wrote: # mount -t extfs2 /dev/ad6s1 /ext2 mount: /dev/ad6s1 : Operation not supported by device The command should include -t ext2fs, not extfs2, as far as I remember. I haven't run Linux for almost 10 years now... I tried several times, with not luck, one of those times i was able to mount it, but not to access it, when i tried to cd /ext2 (folder when is mounted) system tells me that ext2 is not a folder... There are no folders in the UNIX file system hierarchy. The things you're mentioning are called directories. I know, that's just terminology, but it's important to use the correct words context-wise. You don't call the files sheets of paper, do you? :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Blessings Gonzalo Nemmi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: hard disk failure - now what?
On Mon, Aug 24, 2009 at 12:29:19PM -0600, Kelly Martin wrote: I just experienced a hard drive failure on one of my FreeBSD 7.2 production servers with no backup! I am so mad at myself for not backing up!! Welcome to the club. :-) Now it's a salvage operation. Here are the type of errors I was getting on the console, over-and-over: ad4: TIMEOUT - WRITE_DMA48 retrying (0 retries left) LBA=441633503 ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly ad4: FAILURE - WRITE_DMA48 timed out LBA=441633375 g_vgs_done():ad4s1f[WRITE(offset=216338284544, length=16384)]error = 5 It _could_ just be a bad or improperly connected SATA cable. Try changing or re-seating the cable. Read errors cannot damage your data, but write errors can! Immediately stop all writing to the disk. Re-mount the partitions on that disk as read-only, or unmount them. To see if a disk really is broken, install sysutils/smartmontools, and run 'smartctl -a' on the disk. If you see errors in its report (e.g. reallocated sectors), the disk is dying and should be unplugged to prevent it from getting worse. My question: what kind of checks and/or repair tools should I run on the damaged drive after it's mounted? As others have mentioned, first make a copy (with the disk unmounted) of the partitions on that disk with dd, saving them to another drive. That way you can experiment with the data without further deterioration of the original. You can use this disk image e.g. as a vnode-backed memory disk, see mdconfig(8). If you cannot get a good copy of the disk partitions it might be a good idea to get a quote from a professional hard drive data recovery company to do that for you. I've never had occasion to try this (hooray for backups) but I've heard it can be quite expensive. :-/ Try using fsck_ffs on (copies of) the disk image to see if that can restore the damage. If the damage is beyond repair for fsck_ffs, you have a real problem. Of course is you have a good disk image, your data is still there, but you might have to use a forensics program like sysutils/sleuthkit or hexdump to try and piece files together. And even then you cannot be sure that there is no corrupted data in the files themselves. Good luck with that. :-( Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpG8KHu4CLdA.pgp Description: PGP signature
Re: Equivilant of 'lsmod'
On Mon, Aug 24, 2009 at 01:58:39PM -0700, Charlie Kester wrote: On Mon 24 Aug 2009 at 12:44:38 PDT Dunc wrote: I think he wanted to know what the equivalent of the Linux 'lsmod' command is. Is kldstat 100% semantically congruent with lsmod? I.e., are there things you can do with lsmod that you can't with kldstat? A quick comparison of the manpages will probably give the answer, but it will save everyone some time if the OP explains what he wants to do that he would have used lsmod for if this were Linux. Besides, not everyone here is familiar with Linux and not everyone wants to spend any time learning it. Just giving the Linux command for something means you're unnecessarily narrowing down the number of people who can give you an answer. Don't confuse the issue with facts! -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] Quoth Richard Pattis: If you cannot grok the overall structure of a program while taking a shower, e.g., with no external memory aids, you are not ready to code it. pgpBnAS6lOtli.pgp Description: PGP signature
Re: moving a disk
Roland Smith wrote: On Mon, Aug 24, 2009 at 02:33:25PM -0400, PJ wrote: I'm afraid I was a bit impatient Patience is a virtue. Installing stuff can take hours, and a split-second can suffice to screw it all up. Been there done that. :-) and messed up the already messed up disk... frankly, I don't recall whatever happened to the thing in the first place. Can I give you a tip? If you are doing something new or hairy, keep a laptop or even a paper notebook handy and make notes of what you do. Write down the commands that you use and any error messages that you get. My favorite technique is to open emacs (preferably on another machine), start a terminal/ssh session inside an emacs buffer and then do my thing. This gives me a complete record of what I've done. Save these session (with some added explanations) to a file and you'll know what to do next time, or at least you can explain to others what you've been doing. anyway, I'm just practicing another minimal install... it's not as bad as I had thought... I'm getting it all together now. There is an extremely easy way to get all ports that you need onto a new machine, provided that you have a (base) machine of (a) the same FreeBSD major version of (b) the same hardware architecture and (c) up-to-date installed ports available. On the base machine, make dump(8)s of the filesystem(s) containing /usr/local, /var/db/ports and /var/db/pkg and save them to files. Transfer those dump files to an external harddisk or DVD. Using restore(8) interactively on the new machine, restore these three directories to their respective filesystems and you've got all ports up and running save for some editing of /etc/rc.conf. I'm not that organized, yet... ;-) but I have saved my rc.conf, smb.conf, httpd.conf. httpd-vhosts.conf 7 a number of other handy configuration files that I copy to new installations and tweak, if necessary; even the certificates for ssl work fine... so, now I think I'll follow your suggestion and keep a record and do the copy stuff - it also saves bandwidth so you don' t have to download all the distfiles... but I don't do any hairy stuff :-( just trying to K.I.S.S - and this will make it even simpler. Thanks again... learned again... Thanks much, I'm beginning to understand a bit more... this boot stuff sure is complicated... Yep. PC booting is a throwback to an earlier era when 640 kB RAM was all there was and 512 bytes seemed big enough for boot code, because you were writing in machine language or assembly anyway. If you want a real hair-raising story about the time that assemblers were luxuries, google 'the story of Mel' and be amazed (or horrified). It predates PCs, but I think it shows the mind-set of the begin time of (personal) computing. Roland ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
CD writing fails on P6T motherboard with Pioneer cdwriter
Ever since I upgraded to P6T motherboard I can't burn any data or audio
CDs/DVDs.
My dvd-writer ('PIONEER ' 'DVD-RW DVR-112D' '1.21' Removable CD-ROM)
burned CDs ok on the older motherboard/CPU combination.
And now trying to burn audio-cd I got the log below.
What might be wrong?
7.2-STABLE
Yuri
--- command ---
cdrecord dev=5,0,0 speed=4 -v -dao -pad -useinfo -text *.wav
--- log ---
Cdrecord-Clone 2.01 (i386-unknown-freebsd7.2) Copyright (C) 1995-2004
J�rg Schilling
TOC Type: 0 = CD-DA
scsidev: '5,0,0'
scsibus: 5 target: 0 lun: 0
Using libscg version 'schily-0.8'.
SCSI buffer size: 64512
atapi: 0
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'PIONEER '
Identifikation : 'DVD-RW DVR-112D'
Revision : '1.21'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009
Profile: 0x002B
Profile: 0x001B
Profile: 0x001A
Profile: 0x0016
Profile: 0x0015
Profile: 0x0014
Profile: 0x0013
Profile: 0x0011
Profile: 0x0010
Profile: 0x000A
Profile: 0x0009 (current)
Profile: 0x0008
cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support
code.
cdrecord: If you need DVD-R/DVD-RW support, ask the Author for
cdrecord-ProDVD.
cdrecord: Free test versions and free keys for personal use are at
ftp://ftp.berlios.de/pub/cdrecord/ProDVD/
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1267712 = 1238 KB
FIFO size : 4194304 = 4096 KB
pregap1: -1
Track 01: audio 54 MB (05:24.16) no preemp
Track 02: audio 41 MB (04:05.64) no preemp pregapsize: 395
Track 03: audio 56 MB (05:38.76) no preemp pregapsize: 388
Track 04: audio 67 MB (06:42.04) no preemp pregapsize: 425
Track 05: audio 29 MB (02:56.33) no preemp pregapsize: 500
Track 06: audio 84 MB (08:19.46) no preemp pregapsize: 518
Track 07: audio 57 MB (05:39.86) no preemp pregapsize: 380
Track 08: audio 32 MB (03:11.06) no preemp pregapsize: 578
Track 09: audio 40 MB (03:59.80) no preemp pregapsize: 340
Track 10: audio 95 MB (09:27.22) no preemp pregapsize: 305
Track 11: audio 27 MB (02:41.44) no preemp pregapsize: 332
Total size: 586 MB (58:05.80) = 261435 sectors
Lout start: 586 MB (58:07/60) = 261435 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 5
Is not unrestricted
Is not erasable
Disk sub type: Medium Type B, low Beta category (B-) (4)
ATIP start of lead in: -11834 (97:24/16)
ATIP start of lead out: 359849 (79:59/74)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 24
Manufacturer: SONY Corporation
Blocks total: 359849 Blocks current: 359849 Blocks remaining: 98414
Starting to write CD/DVD at speed 4 in real SAO mode for single session.
Last chance to quit, starting real write 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
BURN-Free is ON.
Turning BURN-Free off
Performing OPC...
Sending CUE sheet...
SAO startsec: -11834
Writing lead-in...
Lead-in write time: 50.242s
Writing pregap for track 1 at -150
cdrecord: faio_wait_on_buffer for writer timed out.
cdrecord: Input/output error. write_g1: scsi sendcmd: cmd timeout after
201.726 (200) s
CDB: 2A 00 FF FF FF 6A 00 00 1B 00
cmd finished after 201.726s timeout 200s
write track pad data: error after 0 bytes
BFree: 1128 K BSize: 1152 K
Starting new track at sector: 0
Track 01: 0 of 54 MB written.cdrecord: Input/output error. write_g1:
scsi sendcmd: cmd timeout after 201.735 (200) s
CDB: 2A 00 00 00 00 00 00 00 1B 00
cmd finished after 201.735s timeout 200s
write track data: error after 0 bytes
cdrecord: A write error occured.
cdrecord: Please properly read the error message above.
cdrecord: Input/output error. prevent/allow medium removal: scsi
sendcmd: retryable error
CDB: 1E 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 06 00 00 00 00 0E 00 00 00 00 29 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00
Sense Key: 0x6 Unit Attention, Segment 0
Sense Code: 0x29 Qual 0x00 (power on, reset, or bus device reset
occurred) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 206.776s timeout 200s
Writing time: 463.803s
Average write speed 8.4x.
Fixating...
Fixating time: 6.154s
cdrecord: fifo had 64 puts and 1 gets.
cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%.
--- dmesg log ---
acd0: FAILURE - READ_DVD_STRUCTURE ILLEGAL REQUEST asc=0x30 ascq=0x02
acd0: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00
sks=0x4d 0x00 0x02
acd0: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00
sks=0x4d 0x00 0x02
acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 ascq=0x00
acd0: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00
sks=0x4d 0x00 0x02
acd0: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00
sks=0x4d 0x00 0x02
acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00
acd0: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24
amd automounting daemon is unreliable
I'm having some troublesome issues with filesystems mounted with amd in
FreeBSD 7.2-RELEASE
We have a backend file server wwith sharenfs attributes from ZFS
displaying NFS mountpoints to our front end machines:-
tank/export mountpoint /export local
tank/export sharenfs -maproot=0:0 server1 server2 local
and we have amd automounting directories on the backend file system
/etc/amd.d/amd.map.export:-
/defaults type:=nfs;rhost:=wrfs;opts:=rw,vers=3,proto=udp,nodev
* rfs=/export/files/${key}
/etc/rc.conf:-
amd_enable=YES
amd_flags=-a /.amd_mnt -l syslog /files /etc/amd.d/amd.map.export
There are a bunch of subdirectories in /files which get mounted across
the network when they are accessed on the front-end, and as a solution -
this has been working well.
...the PROBLEM is that it is unreliable. Sometimes amd hangs, and a
mounted directory - while listed in df becomes inaccessible and I get
Permission Denied errors while trying to access the mounted directory.
I'm using some monitoring on the amd process, but as it doesn't die to
trigger an alert, I have to wait until someone tells me that the
filesystem is rejecting them in order to respond tot he issue.
It also happens way too often for me to continue using this solution.
Unless I script amd to restart itself continuously in the event of a
crash... I cannot use it in a production environment.
--
フュージョン・ネットワークサービス株式会社 ■楽天ブロードバンド■
GOL事業部 システム技術部 ネットワーク・オペレションズ グループ
Nathan Butcher / phone +81-50-5527-3611 / fax +81-3-3262-2224
https://secure3.gol.com/mod-pl/ols/index.cgi/?intr_id=F-2xsg6jS4u655
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
