Dump/restore to clone disk
I have seen this posted in the questions archives to be used to clone a active system hard drive to a USB cabled hard drive. Prepare the target #dd if=/dev/zero of=/dev/da0 count=2 # fdisk -BI /dev/da0 # bsdlabel -B -w da0s1 # newfs –U /dev/da0s1a # / # newfs -U /dev/da0s1d # /var # newfs -U /dev/da0s1e # /tmp # newfs -U /dev/da0s1f # /usr Mount target file system ‘a’ # mount /dev/da0s1a /mnt # cd /mnt # dump -0Lauf - /dev/ad1s1a | restore -rf - # cd / # umount /mnt Mount target file system ‘d’ # mount /dev/da0s1d /mnt # cd /mnt # dump -0Lauf - /dev/ad1s1d | restore -rf - # cd / # umount /mnt Mount target file system ‘e’ # mount /dev/da0s1e /mnt # cd /mnt # dump -0Lauf - /dev/ad1s1e | restore -rf - # cd / # umount /mnt Mount target file system ‘f’ # mount /dev/da0s1f /mnt # cd /mnt # dump -0Lauf - /dev/ad1s1f | restore -rf - # cd / # umount /mnt I have questions about this method. What happened to swap? The fstab will be showing it as the first file system on the hard drive slice. Is something missing here? What about the file system sizes. Will the restored hard drive have the same file system sizes as the source file system? Is there some way to allocate larger file systems on the target without using sysinstall to prepare the target beforehand? Is there some command to display the file system allocation size? ___ 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: Dump/restore to clone disk
On Mon, 22 Feb 2010 16:33:47 +0800, Aiza aiz...@comclark.com wrote: I have seen this posted in the questions archives to be used to clone a active system hard drive to a USB cabled hard drive. Prepare the target #dd if=/dev/zero of=/dev/da0 count=2 # fdisk -BI /dev/da0 # bsdlabel -B -w da0s1 # newfs –U /dev/da0s1a # / # newfs -U /dev/da0s1d # /var # newfs -U /dev/da0s1e # /tmp # newfs -U /dev/da0s1f # /usr Mount target file system ‘a’ # mount /dev/da0s1a /mnt # cd /mnt # dump -0Lauf - /dev/ad1s1a | restore -rf - # cd / # umount /mnt Mount target file system ‘d’ # mount /dev/da0s1d /mnt # cd /mnt # dump -0Lauf - /dev/ad1s1d | restore -rf - # cd / # umount /mnt Mount target file system ‘e’ # mount /dev/da0s1e /mnt # cd /mnt # dump -0Lauf - /dev/ad1s1e | restore -rf - # cd / # umount /mnt Mount target file system ‘f’ # mount /dev/da0s1f /mnt # cd /mnt # dump -0Lauf - /dev/ad1s1f | restore -rf - # cd / # umount /mnt I'd like to suggest successive mounting of the partitions. E. g. as they are nested on the source disk, this can be done on the target disk, too. # mount /dev/ad1s1a /mnt # cd /mnt # dump -0 -f - /dev/ad0s1a | restore -r -f - # mount /dev/ad1s1e /mnt/tmp # cd /mnt/tmp # dump -0 -f - /dev/ad0s1e | restore -r -f - # mount /dev/ad1s1f /mnt/var # cd /mnt/var # dump -0 -f - /dev/ad0s1f | restore -r -f - # mount /dev/ad1s1g /mnt/usr # cd /mnt/usr # dump -0 -f - /dev/ad0s1g | restore -r -f - # mount /dev/ad1s1h /mnt/home # cd /mnt/home # dump -0 -f - /dev/ad0s1h | restore -r -f - And then: # cd / # umount /mnt/home # umount /mnt/usr # umount /mnt/var # umount /mnt/tmp # umount /mnt # sync # halt In the above example, transfer is going from ad0 to ad1. I have questions about this method. What happened to swap? The fstab will be showing it as the first file system on the hard drive slice. Is something missing here? The swap partition does not need to be cloned. Furthermore, I doubt that it is the first partition on the disk, while it MAY be possible that it is the first entry in /etc/fstab. The root partition usually refers to partition a, while the swap partition refers to b. What about the file system sizes. Will the restored hard drive have the same file system sizes as the source file system? The target partitions should be at least as big as the source partitions, and they will be filled up to the point the source partition has data, e. g. partition /usr is 20 GB and has 10 GB data, and it is dumped and restored to a new /usr partition with 30 GB space available, then this new partition will be occupied 1/3 (with 10 GB). Is there some way to allocate larger file systems on the target without using sysinstall to prepare the target beforehand? Yes, sade is such a tool, as well as the usual method of using fdisk, bsdlabel, and newfs. Is there some command to display the file system allocation size? You can always use df -h for this, e. g. % df -h /var Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1e989M384M527M42%/var THis should inspire you how to dimension the new partition. -- 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: Dump/restore to clone disk
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/02/2010 08:33, Aiza wrote: What happened to swap? The fstab will be showing it as the first file system on the hard drive slice. Is something missing here? Swap isn't a filesystem. There's no persistent content in a swap partition, so there's nothing to copy. All you need to do is identify a partition as a swap area within /etc/fstab, and the system will initialise it automatically at boot-time. What about the file system sizes. Will the restored hard drive have the same file system sizes as the source file system? No -- this is not necessary. So long as the target filesystem is sufficiently big to contain all of the contents of your dump, it should work fine. Is there some way to allocate larger file systems on the target without using sysinstall to prepare the target beforehand? Certainly. sysinstall(8) really isn't the right tool for this sort of disk operation once you've got beyond doing an initial installation. For the default combination of UFS+MBR look at the following man pages: * fdisk(8) -- create and manage PC slices on the drive * boot0cfg(8) -- install/configure boot managers (not generally needed) * bsdlabel(8) -- create BSD partition tables within a slice * newfs(8) -- write a filesystem onto a partition There are alternatives nowadays: gpart(8) effectively replaces fdisk and bsdlabel on systems using GPT or EFI or various other technologies. zfs(8) similarly replaces bsdlabel and newfs if you want to use that for managing your disks. For more information see: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-adding.html and succeeding chapters http://lists.freebsd.org/pipermail/freebsd-geom/2009-April/003440.html http://wiki.freebsd.org/ZFS Is there some command to display the file system allocation size? df(1) shows you the size of filesystems, bsdlabel(8) shows you the size of the underlying partitions. Normally the filesystem will completely fill the partition it is created in, but it is possible to increase the size of a partition without increasing the size of the filesystem. There's not much point in doing that, as it just wastes space: growfs(8) can expand a filesystem to match the enclosing partition. To see the size of partitions via bsdlabel(1): # bsdlabel da0s1 # /dev/da0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 67487663 41943044.2BSD 2048 16384 28552 b: 41943040 swap c: 716819670unused0 0 # raw part, don't edit 'size' is given here in units of 512byte sectors -- so the 'a' partiton is 32.2GiB. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuCT00ACgkQ8Mjk52CukIxiBACfWFxImCy9AamOcH3+pafroBCw 404Ani9lZiKoEQzMOx7iQAZycUIS9Wec =a97y -END PGP SIGNATURE- ___ 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
dump warning msgs??
Here is the output messages from a test dump of a live file system / What are the warning messages trying to tell me and more important the expected next file 16454, got 437 message? /mnt dump -0Lauf - /dev/ad0s1a | restore -rf - DUMP: Date of this level 0 dump: Mon Feb 22 21:28:25 2010 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping snapshot of /dev/ad0s1a (/) to standard output DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 171427 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] warning: ./.snap: File exists warning: ./tmp: File exists expected next file 16454, got 437 DUMP: 88.38% done, finished in 0:00 at Mon Feb 22 21:34:06 2010 DUMP: DUMP: 171430 tape blocks DUMP: finished in 343 seconds, throughput 499 KBytes/sec DUMP: level 0 dump on Mon Feb 22 21:28:25 2010 DUMP: DUMP IS DONE # /mnt ___ 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: Dump questions
On Mon, Feb 22, 2010 at 12:23:10PM +0800, Aiza wrote: Jerry McAllister wrote: On Sun, Feb 21, 2010 at 11:03:58AM +0100, Polytropon wrote: On Sun, 21 Feb 2010 11:42:50 +0800, Aiza aiz...@comclark.com wrote: 1. Using the -L flag to create a snapshot of the live running file system. ... Is this the limiting factor that forces a user to use (single user mode) for running dump? The snapshot, as far as the dump is concerned, essentially freezes the condition of the file system so that dump does not see any changes while dump is running. Without the snapshot, files could change or be deleted during the time it takes dump to finish. Dump starts by making its own list, by inode, of all the files to dump. Then it writes out, first the list, then the directories and finally the files and links to the media. If the files change between the time that list is made and things get written to the media, you will have an inaccurate representation of the file system. This can result in error messages if files it expects to be there are missing It can mean that a mangled image of a file is written in the dump. Doing a dump in Single User Mode means stopping activity on the system so there are fewer chances of the above happening. Using -L and doing a snapshot will not prevent a dump from being technically obsolete by the time it gets done, but it will mean that what gets written to media is internally consistent. The list it made will be exactly what is on the backup media and the files are all written completely as they were when the snapshot was taken with no mangling. 2. What is the worse that will happen if dump is run on live file system with out the -L flag? The index list that is written as part of the dump will not reflect what is on the dump media. It may claim a file is there, but it really is not. A file or some files are mangled because they are open and being modified by another process as the dump is reading them. The file may be either an inaccurate image or even completely unreadable. Restore is smart enough to skip over these problems if the file[s] you are looking to restore are not the ones mangled or deleted. But, you could get in to a situation of not being able to restore some things that you have on media. Can dump recognize this situation and issue an error message? I don't remember if dump puts out any useful diagnostic. I think it might tell you if it cannot file a file whose inode is in its list to write. But, it is restore that really notices and complains. If you have room, you can use restore to 'verify' a dump just by doing a restore of it to some extra space (maybe even to /dev/null, though I have never tried that one) and seeing if it makes any complaints. This, of course, is a long way to do this, but it might be valuable if it is essential for that dump to be completely readable in a later situation where the original is not longer available. But, in this situation, then making a -L dump (using a snapshot) is really important or even a single user, filesystem unmounted -L dump. 3. Can dump be told to only dump a particular directory tree? IE /var/log or /usr/port? dump only workes on filesystems/partitions. If you know you will want to make dumps on just that directory tree, that is a reason to make a separate partition/filesystem for it and mount it up. There is no reason that /var/log cannot be in its own partition/filesystem separate from /var and just mounted that way. Of course, you have to make sure that /var gets mounted before /var/log. But, that is not strange. Many people make a separate partition for /usr/home inside of /usr or a /var/db that is mounted inside of /var. Now, you can restore just a single file, group of files or a directory tree out of a dump. You do not have to restore the whole dump. So, you can make a dump of a '/var' filesystem if that is what you have and then if you need to restore just '/var/db' out of it, that is no problem. Just make sure you understand where you are putting it and how you specifiy it in the restore. But, if you just want a backup copy of a directory tree that is not its own partition/filesystem, you must use some other tool, such as tar or possibly rsync. jerry Thank you for the detail insight of how dump functions. Now one more question. Is the dump -L backup file made in a multiple-user-mode environment just as dependable as dump backups made in single-user-mode? No. In multi-user, files are still changing. The snapshot could possibly be made between parts of a change - between different writes to the file, so there could be some inconsistency. In practice this is not a big problem, but, single user with filesystems unmounted is still the most absolute way of making sure a filesystem is quiescent during a dump. jerry
Re: Dump/restore to clone disk
On Mon, Feb 22, 2010 at 04:33:47PM +0800, Aiza wrote: I have seen this posted in the questions archives to be used to clone a active system hard drive to a USB cabled hard drive. Prepare the target #dd if=/dev/zero of=/dev/da0 count=2 # fdisk -BI /dev/da0 # bsdlabel -B -w da0s1 # newfs ?U /dev/da0s1a # / # newfs -U /dev/da0s1d # /var # newfs -U /dev/da0s1e # /tmp # newfs -U /dev/da0s1f # /usr Mount target file system ?a? # mount /dev/da0s1a /mnt # cd /mnt # dump -0Lauf - /dev/ad1s1a | restore -rf - # cd / # umount /mnt Mount target file system ?d? # mount /dev/da0s1d /mnt # cd /mnt # dump -0Lauf - /dev/ad1s1d | restore -rf - # cd / # umount /mnt Mount target file system ?e? # mount /dev/da0s1e /mnt # cd /mnt # dump -0Lauf - /dev/ad1s1e | restore -rf - # cd / # umount /mnt Mount target file system ?f? # mount /dev/da0s1f /mnt # cd /mnt # dump -0Lauf - /dev/ad1s1f | restore -rf - # cd / # umount /mnt I have questions about this method. Some of these questions sound like you have not been studying the documentation as you should. People on this list will quickly lose patience if you do not do your own homework before asking questions. There is nothing so futile as trying to trying to explain something to someone who has not done their homework. What happened to swap? The fstab will be showing it as the first file system on the hard drive slice. Is something missing here? Swap is never backed up. It makes no sense to back up swap. It is just scratch space used by the OS and completely irrelevant to any other system. Try looking in to the documentation. What about the file system sizes. Will the restored hard drive have the same file system sizes as the source file system? Read the documentation. They will have the same size as what you make them. Dump/restore do no create filesystems. They just back up and restore data withing filesystems. You create the partitions yourself. A filesystem is an identifiable - most likely a partition, could be a whole disk, that has had newfs run on it to create a filesystem structure and then mounted to some mount point you have created with mkdir. Is there some way to allocate larger file systems on the target without using sysinstall to prepare the target beforehand? Yes, you use fdisk and bsdlabel and finally newfs. But, you cannot do this willy-nilly on a disk that is already in use. This is well documented. Is there some command to display the file system allocation size? Oh come on. This is all over the documentation. Try: df -k There are lots of other ways you can look up too. jerry ___ 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
Physic to KVM VPS server FREEBSD 8.0 STABLE
Hi All, I have managed to migrate a physic old server to a vps, using KVM. Dumping the HD with dd to a .img file and assigning the hd under KVM. Everything looks alright except for a cdrom driver error (as the original server use to have 2 of them...) I have recompile the kernel without atapi modules on it. but problem still persist. There is any option to reconfigure all the hardware without re-installing, (something like the Repair option for NT systems)? Thanks! -- () ASCII Ribbon Campaign | Against HTML e-mail /\ www.asciiribbon.org | Against proprietary extensions ___ 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: dump warning msgs??
On Mon, Feb 22, 2010 at 09:48:24PM +0800, Aiza wrote: Here is the output messages from a test dump of a live file system / What are the warning messages trying to tell me and more important the expected next file 16454, got 437 message? Looks like it finished OK. Those numbers are inode identifiers. I don't know the exact algorithm dump uses for sorting the inodes, but this looks like a file was deleted between the time the list was made and the time dump got to reading it. That is a message of the sort it makes when those things happen. jerry /mnt dump -0Lauf - /dev/ad0s1a | restore -rf - DUMP: Date of this level 0 dump: Mon Feb 22 21:28:25 2010 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping snapshot of /dev/ad0s1a (/) to standard output DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 171427 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] warning: ./.snap: File exists warning: ./tmp: File exists expected next file 16454, got 437 DUMP: 88.38% done, finished in 0:00 at Mon Feb 22 21:34:06 2010 DUMP: DUMP: 171430 tape blocks DUMP: finished in 343 seconds, throughput 499 KBytes/sec DUMP: level 0 dump on Mon Feb 22 21:28:25 2010 DUMP: DUMP IS DONE # /mnt ___ 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: Dump questions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/02/2010 14:30, Jerry McAllister wrote:
No. In multi-user, files are still changing. The snapshot could
possibly be made between parts of a change - between different writes
to the file, so there could be some inconsistency. In practice this
is not a big problem, but, single user with filesystems unmounted is
still the most absolute way of making sure a filesystem is quiescent
during a dump.
Umm you don't *need* to go to single user to ensure a consistent
filesystem dump: unmounting the partition is sufficient, or remounting
it read-only. It's just that shutting the system down and rebooting to
single user mode can save you a deal of faffing about trying to kill
off any processes still using the filesystem, which would otherwise
block your ability to unmount it.
Note too, it's *reboot* into single user ('shutdown -r now', then press
4 at the boot menu) not *drop* into single user ('shutdown now') which
doesn't unmount filesystems for you, although it should kill almost all
processes.
Single user has it's own disadvantages: generally there's no network
configured, and with the root partition mounted read-only, you can't
update /etc/dumpdates.
Whenever you boot into single user, remember to run 'fsck -p' to ensure
filesystem integrity. I'm not sure what happens if you attempt to
dump'n'restore a dirty filesystem, but it's certainly going to have
unintended consequences if the filesystem is actually damaged rather
than just dirty.
Cheers,
Matthew
- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkuCnkkACgkQ8Mjk52CukIyR+gCfX9rep9S9DQcIcRDqSoAptQX9
gMkAoIV/zhe4kRRlRN8fjn5+W7CS1csM
=6J2U
-END PGP SIGNATURE-
___
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: Physic to KVM VPS server FREEBSD 8.0 STABLE
On Mon, 22 Feb 2010 15:04:02 +, Jeronimo Calvo jeronimocal...@googlemail.com wrote: Hi All, I have managed to migrate a physic old server to a vps, using KVM. Dumping the HD with dd to a .img file and assigning the hd under KVM. Everything looks alright except for a cdrom driver error (as the original server use to have 2 of them...) Could you tell the exact error (error message welcome)? I have recompile the kernel without atapi modules on it. but problem still persist. So then it is using a SCSI type of interface for the CD drive? There is any option to reconfigure all the hardware without re-installing, (something like the Repair option for NT systems)? No, because it isn't needed. FreeBSD automatically loads the drivers for the hardware that is present. Additional hardware can be accessed via loadable modules (which's functionality you can include into the kernel by compiling your own, but it mostly isn't neccessary). Again, a copy of the error message or more detailed explaination of possibly malicious behaviour would really help to recognize the problem, and to help correcting 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
Re: Physic to KVM VPS server FREEBSD 8.0 STABLE
On 02/22/10 16:04, Jeronimo Calvo wrote: Hi All, I have managed to migrate a physic old server to a vps, using KVM. Since you have not explainted what KVM is, I assume it's Linux's virtualization? Dumping the HD with dd to a .img file and assigning the hd under KVM. Everything looks alright except for a cdrom driver error (as the original server use to have 2 of them...) You really need to send all error messages before anyone can comment on your problems. It is very unlikely, practically impossible, that the simple change in the number of CD/DVD devices causes any error by itself. The only (not likely) way this could happen is if you automatically mount the CD devices from fstab, which is usually not done. I have recompile the kernel without atapi modules on it. but problem still persist. Which points to the theory it is not causing your problems. There is any option to reconfigure all the hardware without re-installing, (something like the Repair option for NT systems)? Unix kernels (recent ones) do not configure the hardware in a persistant way like Windows does via the Registry. All hardware is autodetected on boot every time. There is nothing to repair here. You will probably need to send all boot messages received from the FreeBSD system during boot, including the error messages, before anyone can help you. ___ 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: dump warning msgs??
On Monday 22 February 2010, Jerry McAllister wrote: I don't know the exact algorithm dump uses for sorting the inodes, but this looks like a file was deleted between the time the list was made and the time dump got to reading it. I expect it's the inode for the temporary snapshot in the .snap directory. According to the man page this snapshot is unlinked as soon as the dump starts. I assume this is immediately after creating the list of inodes to be backed up, in which case it's in the list but no longer available when the data is dumped. I see the expected xxx, got yyy type of message every time I do a restore from a snapshot dump but it's never caused any problems. I've just done a test dump with the -L option and monitored the contents of the partition's .snap directory, a file named dump_snapshot with inode number 4 appeared as I started the dump and then disappeared. I then tried to restore the entire dump to a temporary destination and got a message expected next file 1319089, got 4. As I expected, the .snapshot directory in the dump was empty with no sign of the dump_snapshot file so I'm assuming that restore put out the warning message when it's list of inodes suggested that number 4 should be the next one but the next sequential file in the dump corresponded to inode 1319089. The wording of the message does however suggest that it actually found the file for inode 4 in the dump when the list of inode numbers indicated that the next sequential file should have been 1319089. I was anticipating the message to be expected next file 4, got 1319089 -- Mike Clarke ___ 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: Limiting Port
On Mon, 22 Feb 2010 05:49:57 -0800 (PST), Alex Terente gmni2...@yahoo.com wrote: Hi, I have a problem with my FreeBSD system, i have installed a gameserver on it and after a period of time, the port 11002 (login port) is closed. What i can do to resolve this? Do you use PF or IPFW for bandwidth and port status control? -- 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: dump warning msgs??
On Mon, 22 Feb 2010 16:37:59 +, Mike Clarke jmc-freeb...@milibyte.co.uk wrote: I see the expected xxx, got yyy type of message every time I do a restore from a snapshot dump but it's never caused any problems. The message is issued by restore, not by dump. According to /usr/src/sbin/restore/restore.c, beginning at line 620, the explaination is: If we find files on the tape that have no corresponding directory entries, then we must have found a file that was created while the dump was in progress. Since we have no name for it, we discard it knowing that it will be on the next incremental tape. This fits the snapshot theory. Use the source, Luke. :-) -- 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: Dump questions
On Sun, Feb 21, 2010 at 03:45:51PM +0800, Aiza wrote: Dan Nelson wrote: In the last episode (Feb 21), Aiza said: 1. Using the -L flag to create a snapshot of the live running file system. Does this mean that a complete copy of the file system is written to .snap directory? No; that would be a copy. Snapshots only copy blocks as they are modified on the parent filesystem, so their size is determined by how much data is modified since the snapshot was created. So how does this interact with the dump process? Dump start reading and writing its dump file and as the live system changes the changes are written to the .snap and when dump completes it overwrites it dump with the changes from the .snap??? No. How does this process work in detail? Go back and read the good and quite complete description someone put in about how snapshotting works a while back in this thread. I think it was Matthew Seaman, but I don't remember for sure. jerry ___ 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: Limiting Port
Alex Terente wrote: Hi, I have a problem with my FreeBSD system, i have installed a gameserver on it and after a period of time, the port 11002 (login port) is closed. What i can do to resolve this? Two things spring to mind at first, possibly a way to get started. First, establish that it is not the game server relinquishing the port. This is unlikely but it ought to get eliminated from consideration. sockstat -4l will tell you what is listening to which ports. Next time it gets closed take a quick look at this and ensure the game server is actually still listening to this port. If it is not it is most likely a configuration detail relevant to the game server. Second, this sounds a lot like a NAT session timing out from inactivity. If such a situation should be the case it is possible to design a rule specific so the ports' traffic can bypass NAT and run straight-through. If the first thingy from above gets eliminated this is where I'd look next. As to exactly how you would go about tailoring such a rule would depend upon the syntax of whichever firewall you are using. -Mike ___ 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
sysinstall on fedora?
hi all... realizing this is a bit OT but i have to deal with this old fedora core 2 machine - making file system, slices, etc... what would be the equivalent utility of sysinstall on fedora? thanks.. ___ 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: sysinstall on fedora?
On Tue, Feb 23, 2010 at 1:06 AM, kalin m ka...@el.net wrote: hi all... realizing this is a bit OT but i have to deal with this old fedora core 2 machine - making file system, slices, etc... what would be the equivalent utility of sysinstall on fedora? Does http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Installation_Guide/s1-diskpartsetup-x86.html help? If you want to automate it, there's kickstart http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Installation_Guide/ch-kickstart2.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: Physic to KVM VPS server FREEBSD 8.0 STABLE
the error that im getting is the following: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 On 22 February 2010 16:02, Ivan Voras ivo...@freebsd.org wrote: On 02/22/10 16:04, Jeronimo Calvo wrote: Hi All, I have managed to migrate a physic old server to a vps, using KVM. Since you have not explainted what KVM is, I assume it's Linux's virtualization? Dumping the HD with dd to a .img file and assigning the hd under KVM. Everything looks alright except for a cdrom driver error (as the original server use to have 2 of them...) You really need to send all error messages before anyone can comment on your problems. It is very unlikely, practically impossible, that the simple change in the number of CD/DVD devices causes any error by itself. The only (not likely) way this could happen is if you automatically mount the CD devices from fstab, which is usually not done. I have recompile the kernel without atapi modules on it. but problem still persist. Which points to the theory it is not causing your problems. There is any option to reconfigure all the hardware without re-installing, (something like the Repair option for NT systems)? Unix kernels (recent ones) do not configure the hardware in a persistant way like Windows does via the Registry. All hardware is autodetected on boot every time. There is nothing to repair here. You will probably need to send all boot messages received from the FreeBSD system during boot, including the error messages, before anyone can help you. ___ 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 -- () ASCII Ribbon Campaign | Against HTML e-mail /\ www.asciiribbon.org | Against proprietary extensions -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.4.9 (GNU/Linux) mQGiBEtdv5MRBADCG3jvP1HPlnWkm+nl0RxB1tgUWO+PvafP4gO+MML0gd11nOWS r/Ql4fTNEzGaNwkEGLHqVAh/UWaWgfbZOU07ukL8mTLkIRDOrTadt+4i+fwlx9Di i/1nI7mOHR6iVgzTg0JJIyrjNSdVs+pd8msaXu2RTO/4eDOLJLKSaYnyRwCg5FH1 KT/a/z73TjD3ebKXjI2xsI0EAJIZMKE4cpLtU44Io8dy6cbCui3+i1dEGaMmabFP hPuaN7pYftPx+wXcg2d4yE0jGq4VvYa/QtgOytOdAOaRr8ROUMvyqnyz4ZfsaZJC z+TbcDpxG4GtHqhCKyNFDjGHuHqqd0JZOLAZCfQWWJZIn+xGiQgvSnZ1AqLUKG1o dVL/BACSIqG5zK+TXD2wJ5Rqk3DtO9I+a5TlvMuXJRig2Y5PjIjdfvPRjUmX4Vrd hp5JJbmKEYIa/tNmmDEK01AEbO7dhJ/ca1fplDCmWxfoudU+ffTnG4OUhN8DHAzQ gg2KBe+EFqy3ILGAkD17p5RRU+xnVpp7IBLLM4qfwOknQ73QlbQkamVyb25pbW9j YWx2b3BAZ29vZ2xlbWFpbC5jb20gPGplcm8+iGAEExECACAFAktdv5MCGyMGCwkI BwMCBBUCCAMEFgIDAQIeAQIXgAAKCRACdTuPJuey9D9eAKCCJZhthT5MSUxAVdOL 9mpu2Xw8GwCg0B803+73WxZlSKcKvQ7+lHPyltG5Ag0ES12/kxAIAIyjx1yAlrVi OKZ3Y6ONlYMq2tddX6RjoR/dTBuGLHSUD0VuWUDXKABChRJQ+Xyfq3izCypxDN6B KVHl2fhTjuFnBXWO8BvsV5NUP9KQZozcGrW6YNCIlcgNrycSCYgVr0X8MuxUX2uc RcLYMPwiR1V9ED7e1nmLryCygpQtNaKv3kbukc8wdo/Dv/TPMmmkG8iIGCR79PWQ DjOvrpVNvAYsUxtzfp3MLuhmeCveY9aA796nCufkMNqYF6kIaQQHJOhLEVk4730A NlKrIAb47Nyn+2DvrKW63OVAVnc1EB6J3F7a6OFQeAhc/p09hkm4APRHa1D8kJuV I4EIUfB+AuMAAwUH/1vFyRDtnWBGVLClImWVMQR92UoHy5j6Nwf2P/aA1rGOZAp4 8ILLctIkoNWSKxnYGjjhsvRJrD0EzYoQYLvR9SbTnTI+BMq7Vsqwo7QyYTeUHtst RXLdw/WEjSH2bba1cgAmC/J/cPj3/oJV9SYJlsodJeuGvZ1rpXDfL0FombcbQsvu s4FuLow2XSVXBQU49L29o1FwUJ7mz44YMKAQZch2XhUoDih52fiXIh8LpAYEcegx 8KvBzKu3HqUhhHe9TwNriUd5j0tY1iSJfAD+IEGXnV7msrd9cGu83s3neajH7acW JCQlvbcs/jQOWGEcKzppo80Aml6rbnGslJuXoh+ISQQYEQIACQUCS12/kwIbDAAK CRACdTuPJuey9DY6AJ9d1hLWSkb7QpZuAIJZBgZBOPXsswCgjgBXroymEAKrl3os t6Oj07t65zQ= =3b9D -END PGP PUBLIC KEY BLOCK- ___ 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: sysinstall on fedora?
On Mon, Feb 22, 2010 at 9:36 PM, kalin m ka...@el.net wrote: hi all... realizing this is a bit OT but i have to deal with this old fedora core 2 machine - making file system, slices, etc... what would be the equivalent utility of sysinstall on fedora? To be honest considering its sooo OLD you're best option is backup and reinstall. And preferably not Fedora of all things, its too dev happy.. CentOS 5.4 will probably serve you better if you have need to run a Linux OS on that device. -- Opportunity is most often missed by people because it is dressed in overalls and looks like work. Thomas Alva Edison Inventor of 1093 patents, including: The light bulb, phonogram and motion pictures. ___ 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: sysinstall on fedora?
thanks.. i'm not going to use it. i have a remote access and just need to mount a usb drive (through a scsi interface?!?!) attached to it so i can copy over some stuff. i was done with redhat when they went enterprise and started modifying the core code basically i just need some command lines like mkfs and such which i couldn't find. i'll check this part command see what it's doing... thanks again... Ross Cameron wrote: On Mon, Feb 22, 2010 at 9:36 PM, kalin m ka...@el.net wrote: hi all... realizing this is a bit OT but i have to deal with this old fedora core 2 machine - making file system, slices, etc... what would be the equivalent utility of sysinstall on fedora? To be honest considering its sooo OLD you're best option is backup and reinstall. And preferably not Fedora of all things, its too dev happy.. CentOS 5.4 will probably serve you better if you have need to run a Linux OS on that device. ___ 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: sysinstall on fedora?
On Tue, Feb 23, 2010 at 1:45 AM, kalin m ka...@el.net wrote: thanks.. i'm not going to use it. i have a remote access and just need to mount a usb drive (through a scsi interface?!?!) attached to it so i can copy over some stuff. i was done with redhat when they went enterprise and started modifying the core code basically i just need some command lines like mkfs and such which i couldn't find. i'll check this part command see what it's doing... In that case you should check fdisk for partitions mkfs for filesystem. You'd be most probably looking for mkfs.ext3 or mkfs.vfat ___ 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: Physic to KVM VPS server FREEBSD 8.0 STABLE
On Mon, 22 Feb 2010 20:00:38 +, Jeronimo Calvo jeronimocal...@googlemail.com wrote: the error that im getting is the following: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 Okay, next question: What are you trying to do when this error occurs? Is it the diagnostic message on startup (when acd drives are inquired regarding their potential content), or when accessing a CD or DVD? The error message indicates, basically, that some process (or program) is asking the drive for something, and the drive doesn't answer back correctly. Very technical explaination, I know. :-) In order to find out if this is a critical message, more information is needed. -- 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: sysinstall on fedora?
Mehul Ved wrote: On Tue, Feb 23, 2010 at 1:45 AM, kalin m ka...@el.net wrote: thanks.. i'm not going to use it. i have a remote access and just need to mount a usb drive (through a scsi interface?!?!) attached to it so i can copy over some stuff. i was done with redhat when they went enterprise and started modifying the core code basically i just need some command lines like mkfs and such which i couldn't find. i'll check this part command see what it's doing... In that case you should check fdisk for partitions mkfs for filesystem. You'd be most probably looking for mkfs.ext3 or mkfs.vfat cool. thanks.. that's what i was looking for ___ 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
IDE ZIP100 Drive
Second attempt to post this to the list. Please bear with me as I'm having issues with my posts to the list not always making it through. OK, after some searching I've come up (almost) empty handed[0-1]. Everything else I've found so far for IOMEGA ZIP100 drives deals with the external drive (either USB or parallel port). I've not seen anything in dmesg or /var/log/messages that would indicate that the device is being detected by anything on boot aside from the BIOS. I'm not sure of the pin selector on the drive but it is cabled as the secondary master (the primary master being my hard drive, of course). I did try mount_msdosfs /dev/ad1s4 /mnt/zip (zip added by me after creating the appropriate directory in /mnt) but came up with mount_msdosfs: /dev/adls4: No such file or directory (there is a disk currently loaded). Does anyone else have any experience with these drives? Are there any docs I'm missing (aside from the FreeBSD Handbook, which is silent about this under-appreciated (and unfortunately over-priced) device[2])? [0]: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/zip-drive/ [1]: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=734560+0+archive/1997/freebsd-questions/19970518.freebsd-questions [2]: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks.html -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Re: if this is a stupid q...
On Mon, Feb 22, 2010 at 12:43:58AM -0600, Dan Nelson wrote: In the last episode (Feb 21), Gary Kline said: Excuse me, butthis IS a stupid question. I've tried to figure it out logically and by experimentation; just want to see if my findings jib with the unix wizards onlist. Now/then i do a portupgrade; I probably should just cron this, but it has given me problems before, so I do it while I can monitor the run. I'll do # portupgrade -akOPv then go ahead and work on other things. Question is What do I renice the run at [ruby] to set it to low at very low-power? I've tried like -17 and +17 (or just 17) because I learned that nice'ing the prio level higher than 0 was giving it a lower prio. Thus the rest of what I was doing could run anmost unaffected. Sometimes I'll be running a vi or two with portupgrade the Only other thing running [compiling, usually], and my editing is extremely slow. Output of vmstat or top during the slowdown might be useful here. If editor responsiveness is bad, you're either running dozens of cpu-hogging processes, or running the system so far out of memory that your editor is being swapped out while you're typing. Certain ports may require a lot of ram to build (the jdk*/openjdk* ports possibly), but none should launch more processes than you have CPUs. Hm. Sometimes ruby is near the top of the list when I check top. Then, sometimes, it vanishes from the top and jumps down the list. AS for cpu-hogging procs, maybe, altho it's hard to see what they might be. I *do* have several instantiations of Konsole running. When i'm upgrading things I try to limit the number of browsers active --Things have been behaving for the past day or so... [??] -- Dan Nelson dnel...@allantgroup.com -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.79a release of Jottings: http://jottings.thought.org/index.php ___ 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: IDE ZIP100 Drive
On 22.02.2010 22:32, Programmer In Training wrote: OK, after some searching I've come up (almost) empty handed[0-1]. Everything else I've found so far for IOMEGA ZIP100 drives deals with the external drive (either USB or parallel port). I've not seen anything in dmesg or /var/log/messages that would indicate that the device is being detected by anything on boot aside from the BIOS. I'm not sure of the pin selector on the drive but it is cabled as the secondary master (the primary master being my hard drive, of course). I did try mount_msdosfs /dev/ad1s4 /mnt/zip (zip added by me after creating the appropriate directory in /mnt) but came up with mount_msdosfs: /dev/adls4: No such file or directory (there is a disk currently loaded). Does anyone else have any experience with these drives? Are there any docs I'm missing (aside from the FreeBSD Handbook, which is silent about this under-appreciated (and unfortunately over-priced) device[2])? I posess one internal with pata interface. Works like a charm though 100Mb is not much. -- Sphinx of black quartz judge my vow. ___ 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: Physic to KVM VPS server FREEBSD 8.0 STABLE
It is basically flooding the terminal at the logon prompt... I was able to connect trough ssh (to avoid the flooding) and remove the cd0 entry from fstab... but error still coming up (I removed it as I dont need a cdrom drive on it now) when decompile the atapi module from kernel now the error is a bit different: UNKNOWN: FAILURE - uknown CMD (0x03) ILLEGAL REQUEST asc=0x20 ascq=0x00 Thanks! Well, this is ocurring all the time... it is basically flooding the terminal... (no so thecn On 22 February 2010 20:29, Polytropon free...@edvax.de wrote: On Mon, 22 Feb 2010 20:00:38 +, Jeronimo Calvo jeronimocal...@googlemail.com wrote: the error that im getting is the following: UNKNOWN: FAILURE - uknown CMD (0x03) ILLEGAL REQUEST asc=0x20 ascq=0x00 Okay, next question: What are you trying to do when this error occurs? Is it the diagnostic message on startup (when acd drives are inquired regarding their potential content), or when accessing a CD or DVD? The error message indicates, basically, that some process (or program) is asking the drive for something, and the drive doesn't answer back correctly. Very technical explaination, I know. :-) In order to find out if this is a critical message, more information is needed. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... -- () ASCII Ribbon Campaign | Against HTML e-mail /\ www.asciiribbon.org | Against proprietary extensions -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.4.9 (GNU/Linux) mQGiBEtdv5MRBADCG3jvP1HPlnWkm+nl0RxB1tgUWO+PvafP4gO+MML0gd11nOWS r/Ql4fTNEzGaNwkEGLHqVAh/UWaWgfbZOU07ukL8mTLkIRDOrTadt+4i+fwlx9Di i/1nI7mOHR6iVgzTg0JJIyrjNSdVs+pd8msaXu2RTO/4eDOLJLKSaYnyRwCg5FH1 KT/a/z73TjD3ebKXjI2xsI0EAJIZMKE4cpLtU44Io8dy6cbCui3+i1dEGaMmabFP hPuaN7pYftPx+wXcg2d4yE0jGq4VvYa/QtgOytOdAOaRr8ROUMvyqnyz4ZfsaZJC z+TbcDpxG4GtHqhCKyNFDjGHuHqqd0JZOLAZCfQWWJZIn+xGiQgvSnZ1AqLUKG1o dVL/BACSIqG5zK+TXD2wJ5Rqk3DtO9I+a5TlvMuXJRig2Y5PjIjdfvPRjUmX4Vrd hp5JJbmKEYIa/tNmmDEK01AEbO7dhJ/ca1fplDCmWxfoudU+ffTnG4OUhN8DHAzQ gg2KBe+EFqy3ILGAkD17p5RRU+xnVpp7IBLLM4qfwOknQ73QlbQkamVyb25pbW9j YWx2b3BAZ29vZ2xlbWFpbC5jb20gPGplcm8+iGAEExECACAFAktdv5MCGyMGCwkI BwMCBBUCCAMEFgIDAQIeAQIXgAAKCRACdTuPJuey9D9eAKCCJZhthT5MSUxAVdOL 9mpu2Xw8GwCg0B803+73WxZlSKcKvQ7+lHPyltG5Ag0ES12/kxAIAIyjx1yAlrVi OKZ3Y6ONlYMq2tddX6RjoR/dTBuGLHSUD0VuWUDXKABChRJQ+Xyfq3izCypxDN6B KVHl2fhTjuFnBXWO8BvsV5NUP9KQZozcGrW6YNCIlcgNrycSCYgVr0X8MuxUX2uc RcLYMPwiR1V9ED7e1nmLryCygpQtNaKv3kbukc8wdo/Dv/TPMmmkG8iIGCR79PWQ DjOvrpVNvAYsUxtzfp3MLuhmeCveY9aA796nCufkMNqYF6kIaQQHJOhLEVk4730A NlKrIAb47Nyn+2DvrKW63OVAVnc1EB6J3F7a6OFQeAhc/p09hkm4APRHa1D8kJuV I4EIUfB+AuMAAwUH/1vFyRDtnWBGVLClImWVMQR92UoHy5j6Nwf2P/aA1rGOZAp4 8ILLctIkoNWSKxnYGjjhsvRJrD0EzYoQYLvR9SbTnTI+BMq7Vsqwo7QyYTeUHtst RXLdw/WEjSH2bba1cgAmC/J/cPj3/oJV9SYJlsodJeuGvZ1rpXDfL0FombcbQsvu s4FuLow2XSVXBQU49L29o1FwUJ7mz44YMKAQZch2XhUoDih52fiXIh8LpAYEcegx 8KvBzKu3HqUhhHe9TwNriUd5j0tY1iSJfAD+IEGXnV7msrd9cGu83s3neajH7acW JCQlvbcs/jQOWGEcKzppo80Aml6rbnGslJuXoh+ISQQYEQIACQUCS12/kwIbDAAK CRACdTuPJuey9DY6AJ9d1hLWSkb7QpZuAIJZBgZBOPXsswCgjgBXroymEAKrl3os t6Oj07t65zQ= =3b9D -END PGP PUBLIC KEY BLOCK- ___ 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: Physic to KVM VPS server FREEBSD 8.0 STABLE
On Mon, 22 Feb 2010 20:58:51 +, Jeronimo Calvo jeronimocal...@googlemail.com wrote: It is basically flooding the terminal at the logon prompt... Is there media inside the drive? Is the drive working properly? I was able to connect trough ssh (to avoid the flooding) and remove the cd0 entry from fstab... but error still coming up (I removed it as I dont need a cdrom drive on it now) Of course; as it seems to me, this message may not have something to do with an actual mounting attempt, so you can leave the fstab entry intact. when decompile the atapi module from kernel now the error is a bit different: UNKNOWN: FAILURE - uknown CMD (0x03) ILLEGAL REQUEST asc=0x20 ascq=0x00 Hmm... interesting. So the error message is printed by the kernel, but not brought into relationship with a certain device. Well, this is ocurring all the time... it is basically flooding the terminal... That's normal, it is a diagnostic message printed out by the kernel. You'll find it in the dmesg output, as well as probably in /var/log/messages and related message files. Still, the question is: Is it related to the drive, or maybe to the controller the drive sits on? -- 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
Gvinum RAID1+0
Hi. Newbie question: I'm trying to figure out how to create a stripe-over-mirrors, aka RAID1+0, with Gvinum. The manual gives an example for a mirror-over-stripes, aka RAID0+1, but I can't for the life of me figure out from that example or others I've feebly Googled how to do a RAID1+0. I'm using 112 drives, so I'd much rather have RAID1+0 than RAID0+1. Does anyone have an example kicking around they could kindly send me? Thanks. Andrew __ Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.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: dump warning msgs??
On Monday 22 February 2010, Polytropon wrote:
On Mon, 22 Feb 2010 16:37:59 +, Mike Clarke
jmc-freeb...@milibyte.co.uk wrote:
I see the expected xxx, got yyy type of message every time I do a
restore from a snapshot dump but it's never caused any problems.
The message is issued by restore, not by dump. According
to /usr/src/sbin/restore/restore.c, beginning at line 620,
the explaination is:
If we find files on the tape that have no corresponding
directory entries, then we must have found a file that
was created while the dump was in progress. Since we have
no name for it, we discard it knowing that it will be
on the next incremental tape.
This fits the snapshot theory. Use the source, Luke. :-)
Yes, I was aware that it was a message from restore and not dump but I
misunderstood how it came about. I think I can see part of what's
happening now. At line 367 in /usr/src/sbin/dump/main.c we have
snprintf(snapname, sizeof snapname,
%s/.snap/dump_snapshot, mntpt);
snprintf(snapcmd, sizeof snapcmd, %s %s %s,
_PATH_MKSNAP_FFS, mntpt, snapname);
unlink(snapname);
if (system(snapcmd) != 0)
errx(X_STARTUP, Cannot create %s: %s\n,
snapname, strerror(errno));
if ((diskfd = open(snapname, O_RDONLY)) 0) {
unlink(snapname);
errx(X_STARTUP, Cannot open %s: %s\n,
snapname, strerror(errno));
}
unlink(snapname);
... so when we make a dump of e.g. /home we've set snapcmd to the
string mksnap_ffs /home /home/.snap/dump_snapshot [1] and then
execute it to create a snapshot. We then open the snapshot and
immediately unlink it. Although this effectively deletes the snapshot
file from the working filesystem it still exists in the snapshot of the
system (and would appear in a directory listing of the snapshot if it
were to be mounted somewhere). At this point I'm starting to get lost
because dump will use the opened snapshot to traverse the system and
will see .snap/dump_snapshot when it maps the files and directories so
this file should be included in the dump and appear in its contents
list but somehow it's present in the dump (although truncated to a zero
length file) but not mapped to any name. I don't see anywhere in the
code where .snap/dump_snapshot might receive any special treatment to
exclude it from the file list, but finding my way through unfamiliar
code is something I'm definitely not very skilled at so I've probably
overlooked something really obvious. Although it's not really a problem
I'm rather curious to understand just how dump handles this.
[1] I'm also puzzled by the use of the command
mksnap_ffs /home /home/.snap/dump_snapshot. According to the man page
I'd have expected just mksnap_ffs /home/.snap/dump_snapshot but quick
experiments show that both forms appear to produce the same result?
--
Mike Clarke
___
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: Physic to KVM VPS server FREEBSD 8.0 STABLE
On 22 February 2010 21:16, Polytropon free...@edvax.de wrote: On Mon, 22 Feb 2010 20:58:51 +, Jeronimo Calvo jeronimocal...@googlemail.com wrote: It is basically flooding the terminal at the logon prompt... Is there media inside the drive? Is the drive working properly? I was able to connect trough ssh (to avoid the flooding) and remove the cd0 entry from fstab... but error still coming up (I removed it as I dont need a cdrom drive on it now) Of course; as it seems to me, this message may not have something to do with an actual mounting attempt, so you can leave the fstab entry intact. when decompile the atapi module from kernel now the error is a bit different: UNKNOWN: FAILURE - uknown CMD (0x03) ILLEGAL REQUEST asc=0x20 ascq=0x00 Hmm... interesting. So the error message is printed by the kernel, but not brought into relationship with a certain device. Well, this is ocurring all the time... it is basically flooding the terminal... That's normal, it is a diagnostic message printed out by the kernel. You'll find it in the dmesg output, as well as probably in /var/log/messages and related message files. How can I get rid of this message, making the system ignore it? Is not causing any apparent problem apart of the funny flooding... Still, the question is: Is it related to the drive, or maybe to the controller the drive sits on? Well, there is not drive itself, so seems to be related to the controller... I have deleted as well the old /dev/* which was assigned previously to the old drive... without any luck... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... -- () ASCII Ribbon Campaign | Against HTML e-mail /\ www.asciiribbon.org | Against proprietary extensions -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.4.9 (GNU/Linux) mQGiBEtdv5MRBADCG3jvP1HPlnWkm+nl0RxB1tgUWO+PvafP4gO+MML0gd11nOWS r/Ql4fTNEzGaNwkEGLHqVAh/UWaWgfbZOU07ukL8mTLkIRDOrTadt+4i+fwlx9Di i/1nI7mOHR6iVgzTg0JJIyrjNSdVs+pd8msaXu2RTO/4eDOLJLKSaYnyRwCg5FH1 KT/a/z73TjD3ebKXjI2xsI0EAJIZMKE4cpLtU44Io8dy6cbCui3+i1dEGaMmabFP hPuaN7pYftPx+wXcg2d4yE0jGq4VvYa/QtgOytOdAOaRr8ROUMvyqnyz4ZfsaZJC z+TbcDpxG4GtHqhCKyNFDjGHuHqqd0JZOLAZCfQWWJZIn+xGiQgvSnZ1AqLUKG1o dVL/BACSIqG5zK+TXD2wJ5Rqk3DtO9I+a5TlvMuXJRig2Y5PjIjdfvPRjUmX4Vrd hp5JJbmKEYIa/tNmmDEK01AEbO7dhJ/ca1fplDCmWxfoudU+ffTnG4OUhN8DHAzQ gg2KBe+EFqy3ILGAkD17p5RRU+xnVpp7IBLLM4qfwOknQ73QlbQkamVyb25pbW9j YWx2b3BAZ29vZ2xlbWFpbC5jb20gPGplcm8+iGAEExECACAFAktdv5MCGyMGCwkI BwMCBBUCCAMEFgIDAQIeAQIXgAAKCRACdTuPJuey9D9eAKCCJZhthT5MSUxAVdOL 9mpu2Xw8GwCg0B803+73WxZlSKcKvQ7+lHPyltG5Ag0ES12/kxAIAIyjx1yAlrVi OKZ3Y6ONlYMq2tddX6RjoR/dTBuGLHSUD0VuWUDXKABChRJQ+Xyfq3izCypxDN6B KVHl2fhTjuFnBXWO8BvsV5NUP9KQZozcGrW6YNCIlcgNrycSCYgVr0X8MuxUX2uc RcLYMPwiR1V9ED7e1nmLryCygpQtNaKv3kbukc8wdo/Dv/TPMmmkG8iIGCR79PWQ DjOvrpVNvAYsUxtzfp3MLuhmeCveY9aA796nCufkMNqYF6kIaQQHJOhLEVk4730A NlKrIAb47Nyn+2DvrKW63OVAVnc1EB6J3F7a6OFQeAhc/p09hkm4APRHa1D8kJuV I4EIUfB+AuMAAwUH/1vFyRDtnWBGVLClImWVMQR92UoHy5j6Nwf2P/aA1rGOZAp4 8ILLctIkoNWSKxnYGjjhsvRJrD0EzYoQYLvR9SbTnTI+BMq7Vsqwo7QyYTeUHtst RXLdw/WEjSH2bba1cgAmC/J/cPj3/oJV9SYJlsodJeuGvZ1rpXDfL0FombcbQsvu s4FuLow2XSVXBQU49L29o1FwUJ7mz44YMKAQZch2XhUoDih52fiXIh8LpAYEcegx 8KvBzKu3HqUhhHe9TwNriUd5j0tY1iSJfAD+IEGXnV7msrd9cGu83s3neajH7acW JCQlvbcs/jQOWGEcKzppo80Aml6rbnGslJuXoh+ISQQYEQIACQUCS12/kwIbDAAK CRACdTuPJuey9DY6AJ9d1hLWSkb7QpZuAIJZBgZBOPXsswCgjgBXroymEAKrl3os t6Oj07t65zQ= =3b9D -END PGP PUBLIC KEY BLOCK- ___ 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
Raid
Hi I have a Hp Pavillion dv8 with dual sata drives. What program do I need to raid this thing. I installed a second hard drive after I bought it.. I am not sure what I need. Thanks, Nick E-mail message checked by Spyware Doctor (7.0.0.514) Database version: 6.14410 http://www.pctools.com/en/spyware-doctor-antivirus/ ___ 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: Raid
Hey Nick Have you read the handbook which is a good starting point for most questions: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html On Tue, Feb 23, 2010 at 5:32 AM, Nick Mackowski nmackow...@new.rr.com wrote: Hi I have a Hp Pavillion dv8 with dual sata drives. What program do I need to raid this thing. I installed a second hard drive after I bought it.. I am not sure what I need. Thanks, Nick E-mail message checked by Spyware Doctor (7.0.0.514) Database version: 6.14410 http://www.pctools.com/en/spyware-doctor-antivirus/ ___ 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
