Re: dhcp server returns core dump when i define network with mask 8
On 23/07/2013 09:03, jb wrote:
s m sam.gh1986 at gmail.com writes:
...
subnet 192.0.0.0 netmask 255.0.0.0 {
range 192.0.0.1 192.255.255.255;
The 'range' denotes IP addresses that can be allocated to clients.
The IP 192.255.255.255 is a reserved broadcast address for the network.
jb
It's definitely bad idea to try to use it, but it doesn't explain the
core dump.
Also, using DHCP to dish out addresses that don't belong to you AND
aren't on a private network (as defined by IANA) will probably lead to
trouble. Valid private address ranges are:
10.0.0.0 - 10.255.255.255 (private class A)
172.16.0.0 - 172.31.255.255 (private class B x 16)
192.168.0.0 - 192.168.255.255 (private class C x 256)
Which block you use is really a matter of taste - classes haven't been
used in routing for quite a while so you can consider them all as
straight blocks but I (for one) still treat them as classed just to help
me visualise what's what. For example, I'll use one class C per site to
prevent conflicts over VPN.
192.0.0.0/24 addresses are allocated to real hosts on the wider
internet, although IIRC some of the lower ones are reserved for use in
documentation (like example.com) - is that where the idea came from?!? :-)
Regards, Frank.
___
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: dhcp server returns core dump when i define network with mask 8
thanks Frank,
192 is just a sample. if i want to define 125.0.0.0 netmask 255.0.0.0, dhcp
server core dump either. you're right, it is better to use just some
limited addresses to avoid possible troubles. but i want to run my dhcp
server for all possible networks.
now my question is: if i define a network with mask 8, the rang should be
like: 126.0.0.0 126.254.255.255?
and thank you jb but if i define my network like below, server runs
correctly:
log-facility local7;
subnet 192.168.0.0 netmask 255.255.0.0 {
range 192.168.0.1 192.168.255.255;
}
i think 192.168.255.55 is reserved for broadcast too. is it not true? if
yes, why dhcp server works correctly?
please help me to clear my mind.
regards,
SAM
On Tue, Jul 23, 2013 at 12:56 PM, Frank Leonhardt fra...@fjl.co.uk wrote:
On 23/07/2013 09:03, jb wrote:
s m sam.gh1986 at gmail.com writes:
...
subnet 192.0.0.0 netmask 255.0.0.0 {
range 192.0.0.1 192.255.255.255;
The 'range' denotes IP addresses that can be allocated to clients.
The IP 192.255.255.255 is a reserved broadcast address for the network.
jb
It's definitely bad idea to try to use it, but it doesn't explain the
core dump.
Also, using DHCP to dish out addresses that don't belong to you AND aren't
on a private network (as defined by IANA) will probably lead to trouble.
Valid private address ranges are:
10.0.0.0 - 10.255.255.255 (private class A)
172.16.0.0 - 172.31.255.255 (private class B x 16)
192.168.0.0 - 192.168.255.255 (private class C x 256)
Which block you use is really a matter of taste - classes haven't been
used in routing for quite a while so you can consider them all as straight
blocks but I (for one) still treat them as classed just to help me
visualise what's what. For example, I'll use one class C per site to
prevent conflicts over VPN.
192.0.0.0/24 addresses are allocated to real hosts on the wider internet,
although IIRC some of the lower ones are reserved for use in documentation
(like example.com) - is that where the idea came from?!? :-)
Regards, Frank.
__**_
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-**
unsubscr...@freebsd.org 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: dhcp server returns core dump when i define network with mask 8
Quoting Frank Leonhardt fra...@fjl.co.uk: There are two common ways of defining a subnet mask - one is a dotted quad (e.g. 255.255.255.0) and the other is with a slash and the number of low-order bits - e.g. 192.168.1.0/8. Eight bits here means you get 2^8 addresses (i.e. 256). Don't use the first and last address in the range - the first is complicated (the network address) and the last is for broadcast packets. This doesn't always hold true but you're unlikely to come across exceptions. This is the wrong way round. the number after the slash indicates the number of bits in the network address - the high-order bits. So, when you say you want to define a network with mask 8 I don't really know what you mean from your example. Do you mean a /8? 192.168.1.0/8 = range 192.168.1.1192.168.1.254 with a subnet mask of 255.255.255.0 (0xFF00) Nope. 192.168.1.0/24 = 192.168.1.1-255 mask 255.255.255.0. 192.168.1.0/8 doesn't start where you think it does (and is arguably the wrong way to specify that network) because all but the first 8 bits are masked out - it's 192.0.0.0 - 192.255.255.255. ___ 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: dhcp server returns core dump when i define network with mask 8
s m sam.gh1986 at gmail.com writes:
and thank you jb but if i define my network like below, server runs
correctly:
log-facility local7;
subnet 192.168.0.0 netmask 255.255.0.0 {
range 192.168.0.1 192.168.255.255;
}
i think 192.168.255.55 is reserved for broadcast too. is it not true? if
yes, why dhcp server works correctly?
please help me to clear my mind.
regards,
SAM
Regarding subnets:
192.168.0.0 netmask 255.255.0.0
is equivalent to
192.168.0.0/16
which splits it into a network id 192.168. and host id .0.0
Another example:
192.168.0.0 netmask 255.0.0.0
is equivalent to
192.168.0.0/8
which splits it into a network id 192. and host id 168.0.0
Regarding broadcast address:
yes, for subnet 192.168.0.0/16 the broadcast ip is 192.168.255.255 .
What are the implications of including broadcast ip in range option ?
Firstly, it depends on how the authors of software, that is DHCP server,
interpreted the dhcpd.conf option data. They could have rejected that
option up front, or accept it (implying you are the boos !).
After all, dhcpd.conf(5) only says:
The range statement
range [ dynamic-bootp ] low-address [ high-address];
For any subnet on which addresses will be assigned dynamically, there
must be at least one range statement. The range statement gives
the lowest and highest IP addresses in a range. All IP addresses in
the range should be in the subnet in which the range statement is declared.
Well, looks good to me so far !
Next, dhcpd.conf(5) describes how DHCP server deals with:
DYNAMIC ADDRESS ALLOCATION
...
IP ADDRESS CONFLICT PREVENTION
...
You can analyse it and see if any trouble lurks there ...
Secondly, let's assume there was no problem and that ip was dispensed to a host.
But, in a different place of IP specs there is a RFC??? which says that
the 192.168.255.255 as a generically valid ip address will assume some
additional meaning, that is it will be treated as a broadcast address
(it will represent all hosts on a subnet).
Wow ! That should give you a pause ...
It is said that the broadcast address is used by an application to send
the same message to all other hosts in the network simultaneously.
Who is using it ?
Well, our client host is using it (let's assume it was assigned that ip
above ...).
What happens when the host sends a packet out with a source ip address of
a broadcast ip address ? One can imagine that the destination host will
respond and send back a packet to a destination ip address which is our
sender's broadcast ip address ... You mean to every host on that network ?
Something fishy is on the way ...
But while doing it, it will utilize some protocols, like ARP, RIP, etc.
In addition, it is said that broadcast messages are typically produced by
network protocols such as the Address Resolution Protocol (ARP) and
the Routing Information Protocol (RIP).
They will utilize that ip broadcast address regardless of the fact that it
has been presumably assigned to the client host too.
Wow, what a soup ...
Enjoy it while it lasts :-)
jb
___
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: dhcp server returns core dump when i define network with mask 8
On 23/07/2013 13:35, j.mcke...@ru.ac.za wrote: Quoting Frank Leonhardt fra...@fjl.co.uk: There are two common ways of defining a subnet mask - one is a dotted quad (e.g. 255.255.255.0) and the other is with a slash and the number of low-order bits - e.g. 192.168.1.0/8. Eight bits here means you get 2^8 addresses (i.e. 256). Don't use the first and last address in the range - the first is complicated (the network address) and the last is for broadcast packets. This doesn't always hold true but you're unlikely to come across exceptions. This is the wrong way round. the number after the slash indicates the number of bits in the network address - the high-order bits. So, when you say you want to define a network with mask 8 I don't really know what you mean from your example. Do you mean a /8? 192.168.1.0/8 = range 192.168.1.1192.168.1.254 with a subnet mask of 255.255.255.0 (0xFF00) Nope. 192.168.1.0/24 = 192.168.1.1-255 mask 255.255.255.0. 192.168.1.0/8 doesn't start where you think it does (and is arguably the wrong way to specify that network) because all but the first 8 bits are masked out - it's 192.0.0.0 - 192.255.255.255. Quite correct - for some reason I got that bit backwards when I'm using it every day the right way around. It's ludicrously hot and humid in London at the moment, lack of sleep caused thereby c... ___ 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
dhcp server returns core dump when i define network with mask 8
hello all,
i have a question about dhcpd in freebsd8.2 . when i define my network like
below in dhcpd.conf file, server doesn't run correctly and return core
dump
this is my dhcpd.conf file:
ddns-update-style none;
log-facility local7;
subnet 192.0.0.0 netmask 255.0.0.0 {
range 192.0.0.1 192.255.255.255;
}
i want to define a network with mask 8. is this config wrong? if yes, how
should i define it?
thanks in advance,
SAM
___
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: dhcp server returns core dump when i define network with mask 8
s m sam.gh1986 at gmail.com writes:
...
subnet 192.0.0.0 netmask 255.0.0.0 {
range 192.0.0.1 192.255.255.255;
The 'range' denotes IP addresses that can be allocated to clients.
The IP 192.255.255.255 is a reserved broadcast address for the network.
jb
___
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: Daily periodic cronjob generates core dump
On Fri, Jun 14, 2013 at 2:48 PM, Greg Larkin glar...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/14/13 6:26 AM, C. L. Martinez wrote: Hi all, I have a FreeBSD 9.1 host (fully patched) with ZFS. Every day I am receiving in security output this message: fbsd.domain.local kernel log messages: +++ /tmp/security.AT1oDecp 2013-06-14 03:02:10.0 + +pid 75930 (try), uid 0: exited on signal 10 (core dumped) pid 76241 +(try), uid 0: exited on signal 10 (core dumped) How can I detect where is the problem?? Thanks. You can safely ignore this message, as it's generated by autotools when you are building your packages with poudriere. See: http://lists.freebsd.org/pipermail/freebsd-questions/2010-February/213026.html Also check section 12.11.3 on this page for more details on suppressing the message: http://www.freebsd.org/doc/en/books/handbook/configtuning-configfiles.html Many thanks Greg. Works. ___ 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
Daily periodic cronjob generates core dump
Hi all, I have a FreeBSD 9.1 host (fully patched) with ZFS. Every day I am receiving in security output this message: fbsd.domain.local kernel log messages: +++ /tmp/security.AT1oDecp 2013-06-14 03:02:10.0 + +pid 75930 (try), uid 0: exited on signal 10 (core dumped) pid 76241 +(try), uid 0: exited on signal 10 (core dumped) How can I detect where is the problem?? 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
Daily periodic cronjob generates core dump
C. L. Martinez writes: I have a FreeBSD 9.1 host (fully patched) with ZFS. Every day I am receiving in security output this message: fbsd.domain.local kernel log messages: +++ /tmp/security.AT1oDecp 2013-06-14 03:02:10.0 + +pid 75930 (try), uid 0: exited on signal 10 (core dumped) pid 76241 +(try), uid 0: exited on signal 10 (core dumped) How can I detect where is the problem?? Have you added anything to the default system crontab? Are there any user crontabs? Robert Huff ___ 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: Daily periodic cronjob generates core dump
On Fri, Jun 14, 2013 at 11:42 AM, Robert Huff roberth...@rcn.com wrote: C. L. Martinez writes: I have a FreeBSD 9.1 host (fully patched) with ZFS. Every day I am receiving in security output this message: fbsd.domain.local kernel log messages: +++ /tmp/security.AT1oDecp 2013-06-14 03:02:10.0 + +pid 75930 (try), uid 0: exited on signal 10 (core dumped) pid 76241 +(try), uid 0: exited on signal 10 (core dumped) How can I detect where is the problem?? Have you added anything to the default system crontab? Are there any user crontabs? Robert Huff I have added a script to rebuild packages every week with poudriere: # /etc/crontab - root's crontab for FreeBSD # # $FreeBSD: release/9.1.0/etc/crontab 194170 2009-06-14 06:37:19Z brian $ # SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin # #minute hourmdaymonth wdaywho command # */5 * * * * root/usr/libexec/atrun # # Save some entropy so that /dev/random can re-seed on boot. */11* * * * operator /usr/libexec/save-entropy # # Rotate log files every hour, if necessary. 0 * * * * rootnewsyslog # # Perform daily/weekly/monthly maintenance. 1 3 * * * rootperiodic daily 15 4 * * 6 rootperiodic weekly 30 5 1 * * rootperiodic monthly # # Adjust the time zone if the CMOS clock keeps local time, as opposed to # UTC time. See adjkerntz(8) for details. 1,310-5 * * * rootadjkerntz -a # # Rebuild all necessary packages for SIEM infrastructure 35 23 * * 4 root/root/bin/build_pkgs all ___ 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: Daily periodic cronjob generates core dump
C. L. Martinez writes: Have you added anything to the default system crontab? Are I have added a script to rebuild packages every week with poudriere: And if you comment that out? Robert Huff ___ 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: Daily periodic cronjob generates core dump
On Fri, Jun 14, 2013 at 12:17 PM, Robert Huff roberth...@rcn.com wrote: C. L. Martinez writes: Have you added anything to the default system crontab? Are I have added a script to rebuild packages every week with poudriere: And if you comment that out? Robert Huff Uhmm .. I will try it ... but for what reason?? ___ 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: Daily periodic cronjob generates core dump
Uhmm .. I will try it ... but for what reason?? It would be nice to see if anything else in the crontab might be causing it. You can also run `periodic security` as root and see if it manfiests the same way. ___ 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: Daily periodic cronjob generates core dump
On Fri, Jun 14, 2013 at 12:30 PM, Jason Birch jbi...@jbirch.net wrote: Uhmm .. I will try it ... but for what reason?? It would be nice to see if anything else in the crontab might be causing it. You can also run `periodic security` as root and see if it manfiests the same way. Running from console, no problem: root@fbsd:~ # periodic security Checking setuid files and devices: Checking negative group permissions: Checking for uids of 0: root 0 toor 0 Checking for passwordless accounts: Checking login.conf permissions: Checking for ports with mismatched checksums: fbsd.domain.local pf denied packets: +++ /tmp/security.NiYRT5WC 2013-06-14 12:44:34.0 + +block drop in log quick on ! lo0 inet from 127.0.0.0/8 to any [ Evaluations: 166898 Packets: 0 Bytes: 0 States: 0 ] +block drop in log quick on ! em0 inet from 172.16.0.0/24 to any [ Evaluations: 132328 Packets: 0 Bytes: 0 States: 0 ] +block drop in log quick inet from 172.16.0.109 to any [ Evaluations: 132328 Packets: 0 Bytes: 0 States: 0 ] +block drop in log quick on ! lo0 inet6 from ::1 to any [ Evaluations: 132328 Packets: 0 Bytes: 0 States: 0 ] +block drop in log all [ Evaluations: 132328 Packets: 128574 Bytes: 12252183 States: 0 ] +block drop in log quick from ossec_fwtable to any [ Evaluations: 132328 Packets: 0 Bytes: 0 States: 0 ] +block drop out log quick from any to ossec_fwtable [ Evaluations: 166898 Packets: 0 Bytes: 0 States: 0 ] fbsd.domain.local login failures: fbsd.domain.local refused connections: -- End of security output -- ___ 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
a copy of ASL dump for acer aspire laptops models
Hi everyone, I need a copy of ACPI Source Language (ASL), '# acpidump-dt copy_model_laptop.asl' of any version of FreeBSD you have the option ACPI always enabled and does not give any problem on ACER laptops. Anyone can send me a copy of your ASL dump ( see above ) of ACER ASPIRE laptops model? Thanks, see 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: a copy of ASL dump for acer aspire laptops models
Hi, Reference: From: Xavier xavierfreebsdquesti...@gmail.com Date: Sun, 26 May 2013 14:21:04 +0200 Xavier wrote: Hi everyone, I need a copy of ACPI Source Language (ASL), '# acpidump-dt copy_model_laptop.asl' of any version of FreeBSD you have the option ACPI always enabled and does not give any problem on ACER laptops. Anyone can send me a copy of your ASL dump ( see above ) of ACER ASPIRE laptops model? Hi, I have an acer/aspire/5741 no problems I'm aware of, so will send you mine. uname -a FreeBSD lapr.js.berklix.net 9.1-RELEASE FreeBSD 9.1-RELEASE #3: Tue Apr 9 14:33:17 CEST 2013 j...@lapr.js.berklix.net:/sys/amd64/compile/LAPR.small amd64 I'm not sure what you mean at you have the option ACPI always enabled and does not give any problem however, sysctl -a | grep -i acpi does show device acpi 136 lines in total, acpidump -dt produces 15,840 lines, so I'll not append to list but private mail you. Anything else you need ? What's wrong ? What you are you chasing ? PS mob...@freebsd.org or a...@freesbd.org would be better best lists for this, not questions@. http://lists.freebsd.org/mailman/listinfo/freebsd-acpi http://lists.freebsd.org/mailman/listinfo/freebsd-mobile so I added cc: freebsd-a...@freebsd.org Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with . Send plain text. No quoted-printable, HTML, base64, multipart/alternative. ___ 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: a copy of ASL dump for acer aspire laptops models
Hi Xavier cc questions@ acpi@ I wrote: acpidump -dt produces 15,840 lines, so I'll not append to list but private mail you. I put it here so others on acpi@ questions@ can look too if they want. http://berklix.com/~jhs/hardware/laptops/acer/aspire/5741/ Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with . Send plain text. No quoted-printable, HTML, base64, multipart/alternative. ___ 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
Subversion load problem- svnadmin: Dump stream contains a malformed header (with no ':')
Hi all, I have problem loading a partial dump of one repository into a new repository. When I try to load a partial dump of the old repository, which paths also corrected, I've got the Checksum mismatch error for a file. When I try to replace the Text-content-md5 field of the file on the dump with the correct one using sed command, another error regarding malformed header is occurred(svnadmin: Dump stream contains a malformed header (with no ':'))! I don't know how to fix this problem and I really need this migration to be done. I've searched a lot but couldn't find any solution. Any suggestions or ideas? ___ 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: restore /usr dump on two hard disk parallel y
thanks Lowell for your reply, i want to restore my /usr dump on both of my disks (each one has /usr partition separately). i try to use TMPDIR in order to prevent this conflict, but restore does not identify it and use my /tmp dir yet. this is what i do: first, i create a tmp1 directory in /tmp directory and set its permission to 777 second, i mount tmp1 into my hard disk number 1 i do these two steps for my hard disk number 2 (create tmp2 in tmp and mount it to hard disk number 2) moreover, this is my restore command: TMPDIR=/tmp/tmp2 restore rf /mnt/dumps/zrdump_usr.dump TMPDIR man page for restore command said: if you use -r option, it uses tmp files with unique name in /tmp directory. as you see, i am using -r in my restore command but conflict happens yet. please let me know how to use TMPDIR or any other solution to avoid conflict in /tmp directory. thanks in advance sam On Wed, Apr 24, 2013 at 4:46 PM, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote: s m sam.gh1...@gmail.com writes: i'm trying to restore DUMP file for partition /usr on tow hard disk parallel y. these two hard are connected to my system (i have freebsd8.2). i use restore command and it uses /tmp directory to restore dump. in restoring dump process, two hard disks try to use /tmp directory of my system. therefore conflict happened and restore command return error. i try to use TMPDIR and define another tmp directory for one of my hard disk but it does not identify it and use my system tmp directory yet. please let me know if using TMPDIR is a good idea and how i can use it. if not, how i can restore /usr dump file on two hard disk parallel y? What do you want to do exactly? Do you want both disks together to be your new /usr/partition? In that case, you want to set up some kind of RAID system with the two disks. Start with the GEOM section in the handbook. Do you want to end up with two partitions, each holding part of what the /usr backup contains? If that's what you're after, then the best approach is probably to pick one subdirectory of /usr (/usr/local would be an obvious choice) and restore everything *but* that to one of your disks, then mount the other disk on the subdirectory and restore the rest onto there. If your problem is just that the two restore operations are stepping on each other's temporary files, then TMPDIR *should* take care of that. You could show us more detail of how you run the restore operations, or just run them one at a time instead of in parallel. I hope that helps. ___ 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
restore /usr dump on two hard disk parallel y
hello guys i'm trying to restore DUMP file for partition /usr on tow hard disk parallel y. these two hard are connected to my system (i have freebsd8.2). i use restore command and it uses /tmp directory to restore dump. in restoring dump process, two hard disks try to use /tmp directory of my system. therefore conflict happened and restore command return error. i try to use TMPDIR and define another tmp directory for one of my hard disk but it does not identify it and use my system tmp directory yet. please let me know if using TMPDIR is a good idea and how i can use it. if not, how i can restore /usr dump file on two hard disk parallel y? thanks in advance sam ___ 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: restore /usr dump on two hard disk parallel y
s m sam.gh1...@gmail.com writes: i'm trying to restore DUMP file for partition /usr on tow hard disk parallel y. these two hard are connected to my system (i have freebsd8.2). i use restore command and it uses /tmp directory to restore dump. in restoring dump process, two hard disks try to use /tmp directory of my system. therefore conflict happened and restore command return error. i try to use TMPDIR and define another tmp directory for one of my hard disk but it does not identify it and use my system tmp directory yet. please let me know if using TMPDIR is a good idea and how i can use it. if not, how i can restore /usr dump file on two hard disk parallel y? What do you want to do exactly? Do you want both disks together to be your new /usr/partition? In that case, you want to set up some kind of RAID system with the two disks. Start with the GEOM section in the handbook. Do you want to end up with two partitions, each holding part of what the /usr backup contains? If that's what you're after, then the best approach is probably to pick one subdirectory of /usr (/usr/local would be an obvious choice) and restore everything *but* that to one of your disks, then mount the other disk on the subdirectory and restore the rest onto there. If your problem is just that the two restore operations are stepping on each other's temporary files, then TMPDIR *should* take care of that. You could show us more detail of how you run the restore operations, or just run them one at a time instead of in parallel. I hope that helps. ___ 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 locking up system
(While the system involved is -CURRENT, this doesn't seem to have anything CURRENT-related.) On a system running: FreeBSD 10.0-CURRENT #0: Sun Dec 30 12:52:09 EST 2012 amd64 running dump causes the system to lock up ... sometimes. Specifics: I have a cron job which runs at 0200 local; it dumps three filesystems - /, /var, and /usr - to an external hard drive attached by eSATA. (Dump is incremental Tuesday through Sunday, full on Monday.) After some time of working transparently, this now semi- reliably causes the system to lock up requiring power-off to fix. a) According to dumpdates, the dump of / always completes. Only dumping /var or /usr cause the lock-up. b) There's nothing else in cron running about that time. c) Top doesn't show any suspicious processes or activity. d) When doing fsck on re-boot, the only thing suspicious is a file - caught in fsck phase 1 - large enough to be the usused space on the disk. e) The dump is run in snapshot mode; this has not previously been a problem. f) The exact command used is: dump $DUMP_LEVEL -D $DUMPDATES_FILE -C $DUMP_CACHE -b 64 -Lau -f $DUMP_DATE.var.dump /var where all of the $VARs are appropriately defined elsewhere. g) When run outside the cron environment, the script always runs to completion. Two possibilities come to mind: some kind of hardware failure, or a subtle corruption of the file system. Please - someone out there hav a better idea. ResEpoectfully, Robert Huff ___ 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 just had a crash, core dump
My system 9.1-RELEASE ll /var/crash/ total 697996 -rw-r--r-- 1 root wheel 2 14 Mar 12:51 bounds -rw--- 1 root wheel 577047 14 Mar 12:52 core.txt.0 -rw--- 1 root wheel460 14 Mar 12:51 info.0 -rw-r--r-- 1 root wheel 5 4 Dec 10:34 minfree -rw--- 1 root wheel 784556032 14 Mar 12:52 vmcore.0 Who would be interested in this? /Leslie ___ 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: I just had a crash, core dump
2013-03-14 14:55, Damien Fleuriot skrev: On 14 Mar 2013, at 12:57, Leslie Jensen les...@eskk.nu wrote: My system 9.1-RELEASE ll /var/crash/ total 697996 -rw-r--r-- 1 root wheel 2 14 Mar 12:51 bounds -rw--- 1 root wheel 577047 14 Mar 12:52 core.txt.0 -rw--- 1 root wheel460 14 Mar 12:51 info.0 -rw-r--r-- 1 root wheel 5 4 Dec 10:34 minfree -rw--- 1 root wheel 784556032 14 Mar 12:52 vmcore.0 Who would be interested in this? /Leslie You, I assume ? ___ 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 Yes of course! Unfortunately I do not know what to do with this information. I thought that maybe it could be useful for someone working on development of FreeBSD. Thanks /Leslie ___ 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: I just had a crash, core dump
On Thu, Mar 14, 2013 at 3:45 PM, Leslie Jensen les...@eskk.nu wrote: 2013-03-14 14:55, Damien Fleuriot skrev: On 14 Mar 2013, at 12:57, Leslie Jensen les...@eskk.nu wrote: My system 9.1-RELEASE ll /var/crash/ total 697996 -rw-r--r-- 1 root wheel 2 14 Mar 12:51 bounds -rw--- 1 root wheel 577047 14 Mar 12:52 core.txt.0 -rw--- 1 root wheel460 14 Mar 12:51 info.0 -rw-r--r-- 1 root wheel 5 4 Dec 10:34 minfree -rw--- 1 root wheel 784556032 14 Mar 12:52 vmcore.0 Who would be interested in this? /Leslie You, I assume ? ___ 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 Yes of course! Unfortunately I do not know what to do with this information. I thought that maybe it could be useful for someone working on development of FreeBSD. Take a look at this[1] and try to extract a backtrace. Post it again to see if it catches the attention of a kernel hacker ;) Cheers [1] http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html Thanks /Leslie ___ 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
dump issue
Will someone please confirm or deny that (UFS) journaling and dump -L continue to be incompatible? Respectfully, Robert Huff ___ 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 issue
Snapshots are not yet supported when running with journaled soft updates: Operation not supported :-( On Mon, Feb 11, 2013 at 7:27 AM, Robert Huff roberth...@rcn.com wrote: Will someone please confirm or deny that (UFS) journaling and dump -L continue to be incompatible? Respectfully, Robert Huff ___ 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
kernel panic leads to core dump
I was going ahead and attempting to install libreoffice 3.5.7 and it was going along nicely until the kernel panicked. When I rebooted, I tried to start the install again but it aborted so I went to make clean in /usr/ports/editors/libreoffice when the kernel panicked again. I have two of all the core dump files (one set from each). makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols Is already enabled in the generic (amd64) kernel. $ uname -a FreeBSD alex-laptop 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 -- Yours in Christ, Joseph A Nagy Jr Whoever loves instruction loves knowledge, But he who hates correction is stupid. -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.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
dump date and use of -r or -R
hmmm... I used -R when doing a dump, and I see the dump date is recorded as 1969. Does that mean an incremental dump will dump the whole thing again? on a related note, if dumping to a file and not a linear media such as physical tape, is there any real reason to use -r or -R? ___ 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
ugh. dump / restore problem(s) Cannot find file dump list
I needed to expand a /var partition, which required saving and restoring /var and /usr did the following: booted to backup disk dump -0aR -h 0 -f /usr/backup/dump_var_0_20121113_1920 /dev/ada0p4 (repeat for /tmp, /usr, / partitions to be safe) repartitioned the main disk using gpart newfs the modified partitions (var, tmp, usr) rewrote the boot block and boot partition (#1) mount /dev/ada0p4 /mnt/ssd/var cd /mnt/ssd/var restore -r /usr/backup/dump_var_0_20121113_1920 Cannot find file dump list Any ideas why I get the Cannot find file dump list? What / where is it supposed to be? I was able to get some stuff back from one of the files, but only by doing: #restore -if /usr/backup/dump_usr_0_201121113_1920 restore verbose restore add libdata restore extract Extract requested files You have not read any tapes yet If you are extracting just a few files, start with the last volume and work towards the first; restore can quickly skip tapes that have no further files to extract. Otherwise, begin with volume 1. Specify next volume #: 1 Mount tape volume 1 Enter none if there are no more tapes otherwise enter tape name (default: /usr/backup/dump_usr_0_20121113_1920) unknown tape header type -2 abort [yn] n resync restore, skipped 786 blocks extract file ... ... Add links Set directory mode, owner, and times. Set owner / mode for '.' [yn] y restore If I did not enter Enter after the otherwise enter tape name, but rather entered none I did not get all of the desired contents. Can anyone shed light on this problem? I have been able to restore most everything from a cp I had done at the same time, but I'm not very confident in the results. Fortunately, user data was on a different disk. Obviously, should have done a restore -rN ... before repartitioning. Ugh. Related question: I now realize I should not have answered y to the set owner / mode question, as it changed the mode to the default for root instead of doing what I thought which was restoring the owner / mode to what was saved in the dump. Will restore -x /usr/backup/dump... correct the owner and mode? (and group and flags?) Thanks, Gary ___ 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: ugh. dump / restore problem(s) Cannot find file dump list
El día Wednesday, November 14, 2012 a las 01:20:14AM -0700, Gary Aitken escribió: I needed to expand a /var partition, which required saving and restoring /var and /usr did the following: booted to backup disk dump -0aR -h 0 -f /usr/backup/dump_var_0_20121113_1920 /dev/ada0p4 (repeat for /tmp, /usr, / partitions to be safe) repartitioned the main disk using gpart newfs the modified partitions (var, tmp, usr) rewrote the boot block and boot partition (#1) mount /dev/ada0p4 /mnt/ssd/var cd /mnt/ssd/var restore -r /usr/backup/dump_var_0_20121113_1920 Cannot find file dump list Any ideas why I get the Cannot find file dump list? What / where is it supposed to be? You need to specify the file containing the DUMP with -f flag; and use the flag -r only to restore to the original location, or -x to restore into the current dir; check the man page for details; matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | - No proprietary attachments phone: +49-170-4527211 | - Respect for open standards ___ 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: ugh. dump / restore problem(s) Cannot find file dump list
On Wed, 14 Nov 2012 01:20:14 -0700, Gary Aitken wrote: mount /dev/ada0p4 /mnt/ssd/var cd /mnt/ssd/var restore -r /usr/backup/dump_var_0_20121113_1920 Cannot find file dump list The last command looks wrong. The restore program requires the dump file to be provided via -f, so # restore -rf /usr/backup/dump_var_0_20121113_1920 should work. You can find an example in man restore. -- 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: ugh. dump / restore problem(s) Cannot find file dump list
From: Polytropon free...@edvax.de To: free...@dreamchaser.org Cc: FreeBSD Mailing List freebsd-questions@freebsd.org Sent: Wednesday, November 14, 2012 12:27 PM Subject: Re: ugh. dump / restore problem(s) Cannot find file dump list On Wed, 14 Nov 2012 01:20:14 -0700, Gary Aitken wrote: mount /dev/ada0p4 /mnt/ssd/var cd /mnt/ssd/var restore -r /usr/backup/dump_var_0_20121113_1920 Cannot find file dump list The last command looks wrong. The restore program requires the dump file to be provided via -f, so # restore -rf /usr/backup/dump_var_0_20121113_1920 should work. You can find an example in man restore. Hi There is no - . This is the correct format : restore rf /path/to/dump/files good luck :) ___ 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: ugh. dump / restore problem(s) Cannot find file dump list
El día Wednesday, November 14, 2012 a las 01:01:08AM -0800, Jack Mc Lauren escribió: Hi There is no - . This is the correct format : restore rf /path/to/dump/files from man restore(8): RESTORE(8) FreeBSD System Manager's Manual RESTORE(8) NAME restore, rrestore — restore files or file systems from backups made with dump SYNOPSIS restore -i [-dDhmNuvy] [-b blocksize] [-f file | -P pipecommand] [-s fileno] restore -R [-dDNuvy] [-b blocksize] [-f file | -P pipecommand] [-s fileno] restore -r [-dDNuvy] [-b blocksize] [-f file | -P pipecommand] [-s fileno] restore -t [-dDhNuvy] [-b blocksize] [-f file | -P pipecommand] [-s fileno] [file ...] restore -x [-dDhmNuvy] [-b blocksize] [-f file | -P pipecommand] [-s fileno] [file ...] ... matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | - No proprietary attachments phone: +49-170-4527211 | - Respect for open standards ___ 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: ugh. dump / restore problem(s) Cannot find file dump list
On Wed, 14 Nov 2012 01:01:08 -0800 (PST), Jack Mc Lauren wrote: There is no - . This is the correct format : restore rf /path/to/dump/files Really? The manual at man restore mentions: restore -r [-dDNuvy] [-b blocksize] [-f file | -P pipecommand] [-s fileno] And in the -r section: newfs /dev/da0s1a mount /dev/da0s1a /mnt cd /mnt restore rf /dev/sa0 So it seems that _both_ formats are supported (comparable to tar). One of the (in my opinion) most interesting reference sources for dump/restore also mentions this format: # mount /dev/da0s1 /mnt # mkdir /tmp/oldvar # cd /tmp/oldvar # restore -ruf /mnt/var.dump # umount /mnt Source: http://www.wonkity.com/~wblock/docs/html/backup.html#_em_dump_8_em_em_restore_8_em -- 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: ugh. dump / restore problem(s) Cannot find file dump list
On 11/14/12 01:30, Matthias Apitz wrote: El día Wednesday, November 14, 2012 a las 01:20:14AM -0700, Gary Aitken escribió: I needed to expand a /var partition, which required saving and restoring /var and /usr did the following: booted to backup disk dump -0aR -h 0 -f /usr/backup/dump_var_0_20121113_1920 /dev/ada0p4 (repeat for /tmp, /usr, / partitions to be safe) repartitioned the main disk using gpart newfs the modified partitions (var, tmp, usr) rewrote the boot block and boot partition (#1) mount /dev/ada0p4 /mnt/ssd/var cd /mnt/ssd/var restore -r /usr/backup/dump_var_0_20121113_1920 Cannot find file dump list Any ideas why I get the Cannot find file dump list? What / where is it supposed to be? You need to specify the file containing the DUMP with -f flag; and use the flag -r only to restore to the original location, or -x to restore into the current dir; check the man page for details; Sorry all, a typing issue on my part when composing the email; problem remains: # restore -iN -f /mnt/hd_ssd_backup/usr/backup/dump_tmp_0_20121113_1920 Cannot find file dump list ___ 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: ugh. dump / restore problem(s) Cannot find file dump list
On Wed, 14 Nov 2012, Polytropon wrote: On Wed, 14 Nov 2012 01:01:08 -0800 (PST), Jack Mc Lauren wrote: There is no - . This is the correct format : restore rf /path/to/dump/files Really? The manual at man restore mentions: restore -r [-dDNuvy] [-b blocksize] [-f file | -P pipecommand] [-s fileno] And in the -r section: newfs /dev/da0s1a mount /dev/da0s1a /mnt cd /mnt restore rf /dev/sa0 So it seems that _both_ formats are supported (comparable to tar). One of the (in my opinion) most interesting reference sources for dump/restore also mentions this format: # mount /dev/da0s1 /mnt # mkdir /tmp/oldvar # cd /tmp/oldvar # restore -ruf /mnt/var.dump Yes, -u unlinks an existing file before restoring that file, useful for restoring dumps over an existing filesystem. Leave out the -u when restoring to a new filesystem and the restore will go faster. # umount /mnt And that points out a mistake: /mnt can't be unmounted while it is the PWD. Fixed. Source: http://www.wonkity.com/~wblock/docs/html/backup.html#_em_dump_8_em_em_restore_8_em 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: ugh. dump / restore problem(s) Cannot find file dump list
El día Wednesday, November 14, 2012 a las 09:45:22AM -0700, Warren Block escribió: One of the (in my opinion) most interesting reference sources for dump/restore also mentions this format: # mount /dev/da0s1 /mnt # mkdir /tmp/oldvar # cd /tmp/oldvar # restore -ruf /mnt/var.dump Yes, -u unlinks an existing file before restoring that file, useful for restoring dumps over an existing filesystem. Leave out the -u when restoring to a new filesystem and the restore will go faster. # umount /mnt And that points out a mistake: /mnt can't be unmounted while it is the PWD. Fixed. I think PWD is /tmp/oldvar and not /mnt; matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | - No proprietary attachments phone: +49-170-4527211 | - Respect for open standards ___ 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: Questions about dump/restore to/from DVD media
In message 20121105051447.6eef32ef.free...@edvax.de, Polytropon free...@edvax.de wrote: The problem is that delegating compression to a sub-task would imply that dump cannot precisely adjust its output to match the media size (as the limit is now defined by how good the compression works). Correct. We have both just said the exact same thing in different ways. In order to have _compression_ of the dump data _and_ still be able to divide the (post-compression) data into nice proper 2KB chunks (as required for DVD+/-R writing) the compression step itself would need to be integrated into the dump program itself (and then, for symmetry, if for no other reason, into restore as well). Chunk size _and_ media size matter (as dump would have to know when the media is expected to be nearly-full _with_ compression) Correct. We are both still just violently agreeing. Regards, rfg ___ 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
Questions about dump/restore to/from DVD media
I would like to make a backup of one of my systems using dump(8) in order to be sure that I get everything, including all of the obscure file attribute bits. I would like to make this backup to a _minimal_ number of DVD+R disks. What's the proper procedure for this? In the dump(8) man page, I see the following example: /sbin/dump -0u -L -C16 -B4589840 -P 'growisofs -Z /dev/cd0=/dev/fd/0' /u There are several problems with this example, as far as I am concerned. First I have no particular interest in, or need for _either_ an ISO 9660 _or_ a UDF file system on my backup media. And in fact, that seems to me as if it is likely to be an utter waste of (precious) space on the backup media. Can't I just put the output of the dump command _directly_ onto the output DVD+R media? If so, how would I do this? Would a command such as the following work? /sbin/dump -0u -L -C16 -B4589840 -P 'dd of=/dev/acd0 bs=2048' /u If not, why not? (I already know for sure that I can _read_ everything off of a DVD+R using just dd, so it seems logical that I should likewise be able to write an entire CD using just dd, but I suspect that there may be more to it that this, since I've never seen any references or examples anywhere of anybody writing either CDs or DVDs using dd.) Actually, I just noticed in the dump manpage the -f option. So would this work in place of the above command line? /sbin/dump -0u -L -C16 -B4589840 -f /dev/acd0 /u And if THAT works, then can dump properly sense the actual end-of-media on /dev/acd0, so that the -B option can just be ommitted? Another issue is that I most definitely want to use an absolute minimum of DVD+Rs to store the dump. So I am wondering how I might be able to wedge gzip into this whole process. Could I do something like this? If not, why not? /sbin/dump -0u -L -C16 -B4589840 -P 'gzip | dd of=/dev/acd0 bs=2048' /u Lastly, I want to make a backup of one entire _system_... not just one of the several partitions that compose that system. How exactly can I do this? I mean sure, I can back up each partition separately, using dump, one at a time, but if I do that then the logical implication would seem to be that on the last DVD+R used to make a backup of each of the partitions, there could possibly be a lot of unused/wasted space which could have been used to store the first part of the dump for the next partition in turn. Is there any way to effectively deal with _this_ issue? Regards, rfg ___ 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: Questions about dump/restore to/from DVD media
On Sun, 04 Nov 2012 16:56:58 -0800, Ronald F. Guilmette wrote: I would like to make a backup of one of my systems using dump(8) in order to be sure that I get everything, including all of the obscure file attribute bits. That eliminates at least some tools. I have been using a similar idea in the past to make a backup of a system using multiple CD-Rs and I think cpio or pax, but only for data files that do not come with the whole range of special attributes. Oh wait, it was afio, on FreeBSD 4... I would like to make this backup to a _minimal_ number of DVD+R disks. If you think you can add compression to your files (if it makes sense), it should be incorporated to the command. What's the proper procedure for this? In the dump(8) man page, I see the following example: /sbin/dump -0u -L -C16 -B4589840 -P 'growisofs -Z /dev/cd0=/dev/fd/0' /u There are several problems with this example, as far as I am concerned. First I have no particular interest in, or need for _either_ an ISO 9660 _or_ a UDF file system on my backup media. And in fact, that seems to me as if it is likely to be an utter waste of (precious) space on the backup media. Can't I just put the output of the dump command _directly_ onto the output DVD+R media? I think this command exactly does this. Your idea is correct: There is no need for ISO-9660 or UDF on backup media as it will not be mounted, but processed with the proper restore tool. The command growisofs -Z /dev/cd0=file will record the file like an image to the media. In most cases, that would be an ISO-9660 file system, like growisofs -Z /dev/cd0=stuff.iso (with a premastered file stuff.iso). In _this_ case, the input data is read directly from file descriptor 0, stdin. Whatever appears there, it will be written to the media. Here it is dump's output data stream. If so, how would I do this? Would a command such as the following work? /sbin/dump -0u -L -C16 -B4589840 -P 'dd of=/dev/acd0 bs=2048' /u If not, why not? As far as I know, direct device access for writing does not work here. There are some operating systems that support an approach like this (IRIX for example, if I remember correctly), but FreeBSD doesn't. Depending on your OS version, acd0 != cd0 might appear, being different in access method, i. e. ATAPI vs. ATAPICAM (SCSI over ATA). Actually, I just noticed in the dump manpage the -f option. So would this work in place of the above command line? /sbin/dump -0u -L -C16 -B4589840 -f /dev/acd0 /u And if THAT works, then can dump properly sense the actual end-of-media on /dev/acd0, so that the -B option can just be ommitted? I've never tried if /dev/acd0 (or /dev/cd0 for the reason mentioned above) would be able to start a writing session by receiving data in that kind of way. The -f option is typically used to send data to files, or to - to hand them to another program or pipeline. It seems that doing so for devices (and causing the _physical_ devices to do something with it) is not possible. Another issue is that I most definitely want to use an absolute minimum of DVD+Rs to store the dump. So I am wondering how I might be able to wedge gzip into this whole process. Could I do something like this? If not, why not? /sbin/dump -0u -L -C16 -B4589840 -P 'gzip | dd of=/dev/acd0 bs=2048' /u Taking the initial approach of /sbin/dump -0u -L -C16 -B4589840 -P 'growisofs -Z /dev/cd0=/dev/fd/0' /u it could be something like this: /sbin/dump -0u -L -C16 -B4589840 -P 'gzip | growisofs -Z /dev/cd0=-' /u Not tested, just an idea. Just check how -P interacts with /dev/fd/0 and - for stdin _within_ the pipe command. Lastly, I want to make a backup of one entire _system_... not just one of the several partitions that compose that system. How exactly can I do this? At least not with dump. The dump utility operates on file systems, this means it takes partitions as input. Whatever is _one_ partition can be processed per step. Maybe you could concatenate runs of dump of all the present partitions; however it will be a bit more complicated to restore them using the restore program, which reads file system dumps and outputs the data to initialized and mounted file systems. I mean sure, I can back up each partition separately, using dump, one at a time, but if I do that then the logical implication would seem to be that on the last DVD+R used to make a backup of each of the partitions, there could possibly be a lot of unused/wasted space which could have been used to store the first part of the dump for the next partition in turn. Yes, that is quite possible. In this case, using dd would maybe be better. You would use it to copy the whole disk containing all the partitions, add gzip, break it into multi-volume parts and then record it to DVD+R. Is there any way to effectively deal with _this_ issue? Not per se, but I think all the required parts are in the system, it's just
Re: Questions about dump/restore to/from DVD media
On Sun, Nov 4, 2012 at 4:56 PM, Ronald F. Guilmette r...@tristatelogic.comwrote: I would like to make a backup of one of my systems using dump(8) in order to be sure that I get everything, including all of the obscure file attribute bits. I would like to make this backup to a _minimal_ number of DVD+R disks. What's the proper procedure for this? In the dump(8) man page, I see the following example: /sbin/dump -0u -L -C16 -B4589840 -P 'growisofs -Z /dev/cd0=/dev/fd/0' /u There are several problems with this example, as far as I am concerned. First I have no particular interest in, or need for _either_ an ISO 9660 _or_ a UDF file system on my backup media. And in fact, that seems to me as if it is likely to be an utter waste of (precious) space on the backup media. Can't I just put the output of the dump command _directly_ onto the output DVD+R media? If so, how would I do this? Would a command such as the following work? /sbin/dump -0u -L -C16 -B4589840 -P 'dd of=/dev/acd0 bs=2048' /u If not, why not? (I already know for sure that I can _read_ everything off of a DVD+R using just dd, so it seems logical that I should likewise be able to write an entire CD using just dd, but I suspect that there may be more to it that this, since I've never seen any references or examples anywhere of anybody writing either CDs or DVDs using dd.) Actually, I just noticed in the dump manpage the -f option. So would this work in place of the above command line? /sbin/dump -0u -L -C16 -B4589840 -f /dev/acd0 /u And if THAT works, then can dump properly sense the actual end-of-media on /dev/acd0, so that the -B option can just be ommitted? Another issue is that I most definitely want to use an absolute minimum of DVD+Rs to store the dump. So I am wondering how I might be able to wedge gzip into this whole process. Could I do something like this? If not, why not? /sbin/dump -0u -L -C16 -B4589840 -P 'gzip | dd of=/dev/acd0 bs=2048' /u Lastly, I want to make a backup of one entire _system_... not just one of the several partitions that compose that system. How exactly can I do this? I mean sure, I can back up each partition separately, using dump, one at a time, but if I do that then the logical implication would seem to be that on the last DVD+R used to make a backup of each of the partitions, there could possibly be a lot of unused/wasted space which could have been used to store the first part of the dump for the next partition in turn. Is there any way to effectively deal with _this_ issue? Regards, rfg Assume one file will NOT be copied more than ONE DVD , i.e. , each file will be completely recorded on one DVD : http://en.wikipedia.org/wiki/Cutting_stock_problem Thank you very much . Mehmet Erol Sanliturk ___ 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: Questions about dump/restore to/from DVD media
On 11/05/12 11:18, Polytropon wrote: On Sun, 04 Nov 2012 16:56:58 -0800, Ronald F. Guilmette wrote: I would like to make a backup of one of my systems using dump(8) in order to be sure that I get everything, including all of the obscure file attribute bits. That eliminates at least some tools. I have been using a similar idea in the past to make a backup of a system using multiple CD-Rs and I think cpio or pax, but only for data files that do not come with the whole range of special attributes. Oh wait, it was afio, on FreeBSD 4... I would like to make this backup to a _minimal_ number of DVD+R disks. If you think you can add compression to your files (if it makes sense), it should be incorporated to the command. What's the proper procedure for this? In the dump(8) man page, I see the following example: /sbin/dump -0u -L -C16 -B4589840 -P 'growisofs -Z /dev/cd0=/dev/fd/0' /u There are several problems with this example, as far as I am concerned. First I have no particular interest in, or need for _either_ an ISO 9660 _or_ a UDF file system on my backup media. And in fact, that seems to me as if it is likely to be an utter waste of (precious) space on the backup media. Can't I just put the output of the dump command _directly_ onto the output DVD+R media? I think this command exactly does this. Your idea is correct: There is no need for ISO-9660 or UDF on backup media as it will not be mounted, but processed with the proper restore tool. The command growisofs -Z /dev/cd0=file will record the file like an image to the media. In most cases, that would be an ISO-9660 file system, like growisofs -Z /dev/cd0=stuff.iso (with a premastered file stuff.iso). In _this_ case, the input data is read directly from file descriptor 0, stdin. Whatever appears there, it will be written to the media. Here it is dump's output data stream. If so, how would I do this? Would a command such as the following work? /sbin/dump -0u -L -C16 -B4589840 -P 'dd of=/dev/acd0 bs=2048' /u If not, why not? As far as I know, direct device access for writing does not work here. There are some operating systems that support an approach like this (IRIX for example, if I remember correctly), but FreeBSD doesn't. Depending on your OS version, acd0 != cd0 might appear, being different in access method, i. e. ATAPI vs. ATAPICAM (SCSI over ATA). Actually, I just noticed in the dump manpage the -f option. So would this work in place of the above command line? /sbin/dump -0u -L -C16 -B4589840 -f /dev/acd0 /u And if THAT works, then can dump properly sense the actual end-of-media on /dev/acd0, so that the -B option can just be ommitted? I've never tried if /dev/acd0 (or /dev/cd0 for the reason mentioned above) would be able to start a writing session by receiving data in that kind of way. The -f option is typically used to send data to files, or to - to hand them to another program or pipeline. It seems that doing so for devices (and causing the _physical_ devices to do something with it) is not possible. Another issue is that I most definitely want to use an absolute minimum of DVD+Rs to store the dump. So I am wondering how I might be able to wedge gzip into this whole process. Could I do something like this? If not, why not? /sbin/dump -0u -L -C16 -B4589840 -P 'gzip | dd of=/dev/acd0 bs=2048' /u Taking the initial approach of /sbin/dump -0u -L -C16 -B4589840 -P 'growisofs -Z /dev/cd0=/dev/fd/0' /u it could be something like this: /sbin/dump -0u -L -C16 -B4589840 -P 'gzip | growisofs -Z /dev/cd0=-' /u Not tested, just an idea. Just check how -P interacts with /dev/fd/0 and - for stdin _within_ the pipe command. Lastly, I want to make a backup of one entire _system_... not just one of the several partitions that compose that system. How exactly can I do this? At least not with dump. The dump utility operates on file systems, this means it takes partitions as input. Whatever is _one_ partition can be processed per step. Maybe you could concatenate runs of dump of all the present partitions; however it will be a bit more complicated to restore them using the restore program, which reads file system dumps and outputs the data to initialized and mounted file systems. I mean sure, I can back up each partition separately, using dump, one at a time, but if I do that then the logical implication would seem to be that on the last DVD+R used to make a backup of each of the partitions, there could possibly be a lot of unused/wasted space which could have been used to store the first part of the dump for the next partition in turn. Yes, that is quite possible. In this case, using dd would maybe be better. You would use it to copy the whole disk containing all the partitions, add gzip, break it into multi-volume parts and then record it to DVD+R. Is there any way to effectively deal with _this_ issue? Not per se, but I
Re: Questions about dump/restore to/from DVD media
In message caogwamvoncti7akmtjw0+caastfhfae5gw+pkmh+4ldr00-...@mail.gmail.com Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: Assume one file will NOT be copied more than ONE DVD , i.e. , each file will be completely recorded on one DVD : http://en.wikipedia.org/wiki/Cutting_stock_problem The problem you cited is an interesting one, but I do not believe that it is at all relevant to the current discussion for the simple reason that this cutting problem is based on the assmption that one thing (e.g. a cut piece of paper) cannot be spread across two or more of the available units of raw material (e.g. a standard roll of paper). I'm sure that is true for paper, but as regards to FreeBSD partition backups, these have always been allowed to cross output volume boundaries, I think, e.g. spilling off the end of one backup tape and onto the beginning of the next backup tape. Regards, rfg ___ 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: Questions about dump/restore to/from DVD media
In message 20121105021817.fc5bff1b.free...@edvax.de, Polytropon free...@edvax.de wrote: I would like to make this backup to a _minimal_ number of DVD+R disks. If you think you can add compression to your files (if it makes sense), it should be incorporated to the command. Yes. There really ought to be a -z option integrated into both dump and restore commands. The command growisofs -Z /dev/cd0=file will record the file like an image to the media. In most cases, that would be an ISO-9660 file system, like growisofs -Z /dev/cd0=stuff.iso (with a premastered file stuff.iso). In _this_ case, the input data is read directly from file descriptor 0, stdin. Whatever appears there, it will be written to the media. Ah! OK. I see now. Thank you. If so, how would I do this? Would a command such as the following work? /sbin/dump -0u -L -C16 -B4589840 -P 'dd of=/dev/acd0 bs=2048' /u If not, why not? As far as I know, direct device access for writing does not work here. Yes, apparently not. Bit I _did_ just find something rather interesting in this context. Look at this: http://sg.danny.cz/sg/ddpt.html I have no idea why it isn't already in the ports tree. I'll probably try it out and see if it works. Another issue is that I most definitely want to use an absolute minimum... Taking the initial approach of /sbin/dump -0u -L -C16 -B4589840 -P 'growisofs -Z /dev/cd0=/dev/fd/0' /u it could be something like this: /sbin/dump -0u -L -C16 -B4589840 -P 'gzip | growisofs -Z /dev/cd0=-' /u Yes. I see. That makes sense. But as I said (above) to make this really work right, dump restore really need to have -z options, and do the zipping/unzipping internally. Only if this were available could dump properly deal with end-of-media on any given output volume, I think. Lastly, I want to make a backup of one entire _system_... not just one of the several partitions that compose that system. How exactly can I do this? At least not with dump. The dump utility operates on file systems, this means it takes partitions as input. Whatever is _one_ partition can be processed per step. Well, this is entirely sub-optimal. (I hate to say it, because in general I loath despise Windows, but even Windows has a built-in facility for making a single backup of an _entire_ system, and in a single step, *and*, I presume in a space-efficient manner.) ___ 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: Questions about dump/restore to/from DVD media
On Sun, 04 Nov 2012 18:37:43 -0800, Ronald F. Guilmette wrote: In message 20121105021817.fc5bff1b.free...@edvax.de, Polytropon free...@edvax.de wrote: I would like to make this backup to a _minimal_ number of DVD+R disks. If you think you can add compression to your files (if it makes sense), it should be incorporated to the command. Yes. There really ought to be a -z option integrated into both dump and restore commands. Depending on _what_ kind of compression (gzip, bzip2, 7zip, xz etc.) there might be many of them. If utilizing the capabilities of libarchive is possible, it would be a nice option. Another issue is that I most definitely want to use an absolute minimum... Taking the initial approach of /sbin/dump -0u -L -C16 -B4589840 -P 'growisofs -Z /dev/cd0=/dev/fd/0' /u it could be something like this: /sbin/dump -0u -L -C16 -B4589840 -P 'gzip | growisofs -Z /dev/cd0=-' /u Yes. I see. That makes sense. But as I said (above) to make this really work right, dump restore really need to have -z options, and do the zipping/unzipping internally. Only if this were available could dump properly deal with end-of-media on any given output volume, I think. The problem is that delegating compression to a sub-task would imply that dump cannot precisely adjust its output to match the media size (as the limit is now defined by how good the compression works). Instead an additional step would be required to make sure that a new media for the _compressed_ data stream is requested when it exceeds a certain limit. Additionally restore would have to use a comparable method of chaining the multiple volumes, as it requires operator attention and action. Lastly, I want to make a backup of one entire _system_... not just one of the several partitions that compose that system. How exactly can I do this? At least not with dump. The dump utility operates on file systems, this means it takes partitions as input. Whatever is _one_ partition can be processed per step. Well, this is entirely sub-optimal. It depends on how you did layout your system. Using dump + restore means to operate on partitions. Make the system one partition - deal with one partition. Make many partitions - need to deal with them individually. (I hate to say it, because in general I loath despise Windows, but even Windows has a built-in facility for making a single backup of an _entire_ system, and in a single step, *and*, I presume in a space-efficient manner.) That would be a task for dd. :-) -- 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: Questions about dump/restore to/from DVD media
In message 50971b88.40...@herveybayaustralia.com.au, Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: Also, you may have considered this already (or not :) ), but you are using a direct write to backup your system, and then considering compression on top of that. CD/DVD filesystems incorporate some parity to allow for defects and scratches, so growisofs might be best to use to ensure some integrity to your data. Minimising your space may be good, but a single bit could render all your efforts for nought- especially given the compression leaves no room for error ;) I'm not sure if the error detection/correction on DVDs... either -Rs or +Rs... is a function of the _filesystem_. In fact I don't believe that it is, but I could be wrong. Google for this: DVD+R error correction and there are plenty of references. The ones that I read in the past seemed to suggest that the error detection/correction is a fundamental aspect of how data gets written to both -R and +R disks, totally independent of whether the data being written was organized into any type of filesystem or none at all. In fact, part of the reason that I only use DVD+Rs these days is because I read something that said that something like 1/4 of every block of data on DVD-R disks is not even covered by any error correction code AT ALL. Ah, yes... here is one such reference: http://adterrasperaspera.com/blog/2006/10/30/how-to-choose-cddvd-archival-media The DVD-R specification states that for every 192 bits, 64 of them are not protected under any scheme, 24 of them are protected by 24 bits of parity, and the last 56 bits are protected by another 24 bits of parity. This weird (to put it mildly) scheme allows you to easily scramble or lose 25% of the data that is required to read your disk! This information is almost more important than the actual data burned on the disc itself. The DVD+R specification, however, states that for every 204 bits of information, it is split into four blocks of 52 bits containing 1 sync bit to prevent misreading because of phase changes, 31 bits of data, and a 20 bit parity (that protects all 32 bits of data)... Regards, rfg ___ 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: Questions about dump/restore to/from DVD media
In message 20121105035233.e3c4ae8a.free...@edvax.de, Polytropon free...@edvax.de wrote: But as I said (above) to make this really work right, dump restore really need to have -z options, and do the zipping/unzipping internally. Only if this were available could dump properly deal with end-of-media on any given output volume, I think. The problem is that delegating compression to a sub-task would imply that dump cannot precisely adjust its output to match the media size (as the limit is now defined by how good the compression works). Correct. We have both just said the exact same thing in different ways. In order to have _compression_ of the dump data _and_ still be able to divide the (post-compression) data into nice proper 2KB chunks (as required for DVD+/-R writing) the compression step itself would need to be integrated into the dump program itself (and then, for symmetry, if for no other reason, into restore as well). Using dump + restore means to operate on partitions. Make the system one partition - deal with one partition. Make many partitions - need to deal with them individually. Good point. (I hate to say it, because in general I loath despise Windows, but even Windows has a built-in facility for making a single backup of an _entire_ system, and in a single step, *and*, I presume in a space-efficient manner.) That would be a task for dd. :-) Sorry? I am not following you. How could dd ever substitute for the intelligence of dump(8), and specifically how could it avoid copying of blocks that are ``in'' the filesystem but which are not currently _allocated_ by the filesystem? (I am also not persuaded the dd could handle multiple partitions any better that dump(8) currently does... which is to say not at all, really.) Regards, rfg ___ 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: Questions about dump/restore to/from DVD media
On Sun, 04 Nov 2012 19:49:24 -0800, Ronald F. Guilmette wrote: In message 20121105035233.e3c4ae8a.free...@edvax.de, Polytropon free...@edvax.de wrote: But as I said (above) to make this really work right, dump restore really need to have -z options, and do the zipping/unzipping internally. Only if this were available could dump properly deal with end-of-media on any given output volume, I think. The problem is that delegating compression to a sub-task would imply that dump cannot precisely adjust its output to match the media size (as the limit is now defined by how good the compression works). Correct. We have both just said the exact same thing in different ways. In order to have _compression_ of the dump data _and_ still be able to divide the (post-compression) data into nice proper 2KB chunks (as required for DVD+/-R writing) the compression step itself would need to be integrated into the dump program itself (and then, for symmetry, if for no other reason, into restore as well). Chunk size _and_ media size matter (as dump would have to know when the media is expected to be nearly-full _with_ compression) because the operator will be required to deal with multi-volume media (next DVD). (I hate to say it, because in general I loath despise Windows, but even Windows has a built-in facility for making a single backup of an _entire_ system, and in a single step, *and*, I presume in a space-efficient manner.) That would be a task for dd. :-) Sorry? I am not following you. How could dd ever substitute for the intelligence of dump(8), and specifically how could it avoid copying of blocks that are ``in'' the filesystem but which are not currently _allocated_ by the filesystem? It cannot. :-) With dd, you could copy a disk including all aspects of the present slices and partitions (including file attributes and partitioning data, even boot elements), but it would maybe require a subsequent read and compare step to make sure that everything went well. (I am also not persuaded the dd could handle multiple partitions any better that dump(8) currently does... which is to say not at all, really.) It can - depending on what device you're reading from. Examples: dd if=/dev/ad0s1a - the root partition dd if=/dev/ad0s1- the 1st slice dd if=/dev/ad0 - the whole disk However, dd is very much bare metal and cannot handle multiple volumes and compression natively. It would be neccessary to have all those functionalities scripted additionally. -- 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: Questions about dump/restore to/from DVD media
On 11/05/12 14:14, Polytropon wrote: On Sun, 04 Nov 2012 19:49:24 -0800, Ronald F. Guilmette wrote: In message 20121105035233.e3c4ae8a.free...@edvax.de, Polytropon free...@edvax.de wrote: But as I said (above) to make this really work right, dump restore really need to have -z options, and do the zipping/unzipping internally. Only if this were available could dump properly deal with end-of-media on any given output volume, I think. The problem is that delegating compression to a sub-task would imply that dump cannot precisely adjust its output to match the media size (as the limit is now defined by how good the compression works). Correct. We have both just said the exact same thing in different ways. In order to have _compression_ of the dump data _and_ still be able to divide the (post-compression) data into nice proper 2KB chunks (as required for DVD+/-R writing) the compression step itself would need to be integrated into the dump program itself (and then, for symmetry, if for no other reason, into restore as well). Chunk size _and_ media size matter (as dump would have to know when the media is expected to be nearly-full _with_ compression) because the operator will be required to deal with multi-volume media (next DVD). (I hate to say it, because in general I loath despise Windows, but even Windows has a built-in facility for making a single backup of an _entire_ system, and in a single step, *and*, I presume in a space-efficient manner.) That would be a task for dd. :-) Sorry? I am not following you. How could dd ever substitute for the intelligence of dump(8), and specifically how could it avoid copying of blocks that are ``in'' the filesystem but which are not currently _allocated_ by the filesystem? It cannot. :-) With dd, you could copy a disk including all aspects of the present slices and partitions (including file attributes and partitioning data, even boot elements), but it would maybe require a subsequent read and compare step to make sure that everything went well. (I am also not persuaded the dd could handle multiple partitions any better that dump(8) currently does... which is to say not at all, really.) It can - depending on what device you're reading from. Examples: dd if=/dev/ad0s1a - the root partition dd if=/dev/ad0s1- the 1st slice dd if=/dev/ad0 - the whole disk However, dd is very much bare metal and cannot handle multiple volumes and compression natively. It would be neccessary to have all those functionalities scripted additionally. For reference, if one did backup the whole slice/disk using dd and then compressed the data, would that effectively compress all those 'unallocated' nodes? ___ 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: Questions about dump/restore to/from DVD media
Date: Mon, 05 Nov 2012 15:42:45 +1000 From: Da Rock freebsd-questi...@herveybayaustralia.com.au Subject: Re: Questions about dump/restore to/from DVD media On 11/05/12 14:14, Polytropon wrote: For reference, if one did backup the whole slice/disk using dd and then compressed the data, would that effectively compress all those 'unallocated' nodes? NO. The unallocated' blocks still have whatever data was in them. *IF* you copy /dev/zero to a new file, to fill the disk, then rm -that- file, the compression will be higher. 'How much' depends on how empty the disk 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: system hangs during dump + compress usb2-drive
From: Xin Li delp...@delphij.net To: Jin Guojun jguo...@sbcglobal.net Cc: questi...@freebsd.org; hack...@freebsd.org Sent: Sun, September 30, 2012 1:07:40 PM Subject: Re: system hangs during dump + compress usb2-drive On 9/29/12 10:49 PM, Jin Guojun wrote: In FreeBSD 8.3 release (possibly in earlier release), dump a file system has 2-3GB or more content can cause system hang in a specific case (pipe to compression): dump FS-on-SATA-drive usb-drive OK dump FS-on-SATA-drive | anyCompress sata-drive OK mv a-large-dump-file from STAT drive to a USB drive OK dump small-FS-on-SATA-drive | anyCompress usb-drive OK small -- 1.8GB or less dump large-FS-on-SATA-drive | anyCompress usb-drive hang content is 3GB or larger (did not try around 2GB yet) When system hangs, no sub system, such video, network, etc, will function. Typically, the unfinished compressed dump file is around 1.5-2.7GB, so guessing dumped file content is close to or over 2GB when failure occurred. Has anyone encountered the same problem? Because this usually takes a few hours to occur, this is hard to watch how/when it happens. Is any way to debug or determine what status the system is? For starters I'd use a different console for doing procstat -kk -a and see what the system is doing. (Perhaps also top) I *think* that if it's just hanging for some time, it's probably because the system is trying to take a snapshot? It takes time on UFS when creating and removing the snapshot. Just a guess... Cheers, --- Not sure how to use a different console. No tty is functioning (neither ttyv? nor over network). You are right on a different case -- mount /dev/da0s4d /mnt# mount a usb drive cd /mnt ssh remote-liux-host tar -cf - 8GB_FS | tar -xf - In this case, doing ls -l /mnt or df will hangs, but system is still alive. The network is 45Mbps. I have no idea how long it took the tar to finish since machine is 60 km away. When I left there last Friday, only 400MB was done in one hour. I will get the processing time tomorrow. The problem we can see now is that tar (probably the pipe) process only finish with 4GB. # df Filesystem1K-blocks Used Avail Capacity Mounted on /dev/ad4s3a 1012974355348 57659038%/ devfs 1 1 0 100%/dev ... /dev/da0s4d 1027486774 4198246 941089588 0%/mnt So, I suspect this is a pipe problem, not a compress issue. ___ 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: how restore an unencrypted dump on an encrypted file system?
hi i have a similar problem too. can you explain in detail what you have done step by step? i wanna know if my problem is exactly what you have. thanks On 9/29/12, s m sam.gh1...@gmail.com wrote: thanks Fabian for your answer. i don't know what exactly information is needed but i tell what i did up to now. i have two partition, one is encrypted and the other one is not. the unencrypted partition has boot folder. when i copy FreeBSD base system files, FreeBSD start up correctly but when i restore dump files, FreeBSD doesn't start up correctly. i hope this information help to understand what is wrong. thanks On 9/29/12, Fabian Keil freebsd-lis...@fabiankeil.de wrote: s m sam.gh1...@gmail.com wrote: I backed up my freeBSD 8.2 box by dump command and now want to restore this dump file on an encrypted file system (i used geli to encrypt my file system) but do not know how to do that. is there any way or command to restore an unencrypted dump on an encrypted file system? i tried to restore my dump file as when file system is unencrypted. Can you read the files after attaching the provider manually? this is what i've doe: I decrypted my encrypted file system by geli attach command, then mount it and restore dumps. but when i restart my system, FreeBSD doesn't start up correctly (PXE boot menu is shown and when i select freeBSD, boot.config runs but nothing happend). You do not provide enough information to give a meaningful answer. One possible mistake would be putting the kernel itself on the encrypted file system, but the list of things one can do wrong is pretty long. Fabian ___ 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: how restore an unencrypted dump on an encrypted file system?
thanks saeedeh OK i try to explain what i have done more in detail. i want to restore unencrypted dump files on an encrypted file system. in order to do that, i encrypted my file system by geli command and sure that is done correctly because when i install base and kernel on it, freebsd start up successfully. problem is here: when i restore my dump files and restart my freebsd, boot PXE menu is shown and i select my freebsd but after that, the error message invalid format occurs and i see this message: FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: it selects the default kernel correctly and after some seconds an error message is shown which consists of some hardware addresses. i don't know how to fix it. any hints that might fix my problem are appreciated. On 9/30/12, saeedeh motlagh saeedeh.motl...@gmail.com wrote: hi i have a similar problem too. can you explain in detail what you have done step by step? i wanna know if my problem is exactly what you have. thanks On 9/29/12, s m sam.gh1...@gmail.com wrote: thanks Fabian for your answer. i don't know what exactly information is needed but i tell what i did up to now. i have two partition, one is encrypted and the other one is not. the unencrypted partition has boot folder. when i copy FreeBSD base system files, FreeBSD start up correctly but when i restore dump files, FreeBSD doesn't start up correctly. i hope this information help to understand what is wrong. thanks On 9/29/12, Fabian Keil freebsd-lis...@fabiankeil.de wrote: s m sam.gh1...@gmail.com wrote: I backed up my freeBSD 8.2 box by dump command and now want to restore this dump file on an encrypted file system (i used geli to encrypt my file system) but do not know how to do that. is there any way or command to restore an unencrypted dump on an encrypted file system? i tried to restore my dump file as when file system is unencrypted. Can you read the files after attaching the provider manually? this is what i've doe: I decrypted my encrypted file system by geli attach command, then mount it and restore dumps. but when i restart my system, FreeBSD doesn't start up correctly (PXE boot menu is shown and when i select freeBSD, boot.config runs but nothing happend). You do not provide enough information to give a meaningful answer. One possible mistake would be putting the kernel itself on the encrypted file system, but the list of things one can do wrong is pretty long. Fabian ___ 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: how restore an unencrypted dump on an encrypted file system?
On Sun, Sep 30, 2012 at 10:09 AM, s m sam.gh1...@gmail.com wrote: thanks saeedeh OK i try to explain what i have done more in detail. i want to restore unencrypted dump files on an encrypted file system. in order to do that, i encrypted my file system by geli command and sure that is done correctly because when i install base and kernel on it, freebsd start up successfully. problem is here: when i restore my dump files and restart my freebsd, boot PXE menu is shown and i select my freebsd but after that, the error message invalid format occurs and i see this message: FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: it selects the default kernel correctly and after some seconds an error message is shown which consists of some hardware addresses. i don't know how to fix it. any hints that might fix my problem are appreciated. You could try to let us know what kind of error message you get (i.e. the exact wording). ;-) My guess (out of the blue) is that kernel and modules are now out of sync. This happens when you restore the modules from backup but use a newer kernel (or vice-versa). If you restore stuff from backup, make sure you don't restore anything under your freshly (re-)installed /boot. Or make sure you restore *everything* into /boot, and not just some parts of it. /boot has to be consistent; either everything from the new install, or everything from the backup up install, but not a mix of both. As others pointed out, you need to provide more detailed infos about your backup and restore procedure. It it impossible to guess correctly what you have done otherwise. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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: system hangs during dump + compress usb2-drive
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 9/29/12 10:49 PM, Jin Guojun wrote: In FreeBSD 8.3 release (possibly in earlier release), dump a file system has 2-3GB or more content can cause system hang in a specific case (pipe to compression): dump FS-on-SATA-drive usb-drive OK dump FS-on-SATA-drive | anyCompress sata-drive OK mv a-large-dump-file from STAT drive to a USB drive OK dump small-FS-on-SATA-drive | anyCompress usb-drive OK small -- 1.8GB or less dump large-FS-on-SATA-drive | anyCompress usb-drive hang content is 3GB or larger (did not try around 2GB yet) When system hangs, no sub system, such video, network, etc, will function. Typically, the unfinished compressed dump file is around 1.5-2.7GB, so guessing dumped file content is close to or over 2GB when failure occurred. Has anyone encountered the same problem? Because this usually takes a few hours to occur, this is hard to watch how/when it happens. Is any way to debug or determine what status the system is? For starters I'd use a different console for doing procstat -kk -a and see what the system is doing. (Perhaps also top) I *think* that if it's just hanging for some time, it's probably because the system is trying to take a snapshot? It takes time on UFS when creating and removing the snapshot. Just a guess... Cheers, -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) iQEcBAEBCAAGBQJQaKaIAAoJEG80Jeu8UPuzfH4IAL3k2M/KHV39FrI0U4lZ1yu/ bFbJJubQHzjfNbDrI4er1Xg6S0sN0DNnRoD/bQFKKHvQpfqcCUOwUtpq0kssyfLY 4XQOF9nhcyvL/INz6ArtI7EhKh/2cADb+1zp+NMsFyqvn3F09VPvx6h9z6ufaian LlAA6uisZSl/eGv5uNGGcudiUxSALql8UniZVHJvyO+pCjOAwL+MBxfqQ4LW3DEy ngvkvCeQ2nK/k0oQDq5jt9A9+D+7b3+Wo+4sMkIN7uTMgPpET4JSgWgxkzG1xM+l VMTAUHiqdeKp2JbWot1sRE5K7SiLPDmVGXEa0w+duBbvtuk8M/uXLootky0y1Oc= =zTBM -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
how restore an unencrypted dump on an encrypted file system?
hello guys, I backed up my freeBSD 8.2 box by dump command and now want to restore this dump file on an encrypted file system (i used geli to encrypt my file system) but do not know how to do that. is there any way or command to restore an unencrypted dump on an encrypted file system? i tried to restore my dump file as when file system is unencrypted. this is what i've doe: I decrypted my encrypted file system by geli attach command, then mount it and restore dumps. but when i restart my system, FreeBSD doesn't start up correctly (PXE boot menu is shown and when i select freeBSD, boot.config runs but nothing happend). please let me know how i can fix it or if i do something wrong. yours, sam ___ 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: how restore an unencrypted dump on an encrypted file system?
s m sam.gh1...@gmail.com wrote: I backed up my freeBSD 8.2 box by dump command and now want to restore this dump file on an encrypted file system (i used geli to encrypt my file system) but do not know how to do that. is there any way or command to restore an unencrypted dump on an encrypted file system? i tried to restore my dump file as when file system is unencrypted. Can you read the files after attaching the provider manually? this is what i've doe: I decrypted my encrypted file system by geli attach command, then mount it and restore dumps. but when i restart my system, FreeBSD doesn't start up correctly (PXE boot menu is shown and when i select freeBSD, boot.config runs but nothing happend). You do not provide enough information to give a meaningful answer. One possible mistake would be putting the kernel itself on the encrypted file system, but the list of things one can do wrong is pretty long. Fabian signature.asc Description: PGP signature
Re: how restore an unencrypted dump on an encrypted file system?
thanks Fabian for your answer. i don't know what exactly information is needed but i tell what i did up to now. i have two partition, one is encrypted and the other one is not. the unencrypted partition has boot folder. when i copy FreeBSD base system files, FreeBSD start up correctly but when i restore dump files, FreeBSD doesn't start up correctly. i hope this information help to understand what is wrong. thanks On 9/29/12, Fabian Keil freebsd-lis...@fabiankeil.de wrote: s m sam.gh1...@gmail.com wrote: I backed up my freeBSD 8.2 box by dump command and now want to restore this dump file on an encrypted file system (i used geli to encrypt my file system) but do not know how to do that. is there any way or command to restore an unencrypted dump on an encrypted file system? i tried to restore my dump file as when file system is unencrypted. Can you read the files after attaching the provider manually? this is what i've doe: I decrypted my encrypted file system by geli attach command, then mount it and restore dumps. but when i restart my system, FreeBSD doesn't start up correctly (PXE boot menu is shown and when i select freeBSD, boot.config runs but nothing happend). You do not provide enough information to give a meaningful answer. One possible mistake would be putting the kernel itself on the encrypted file system, but the list of things one can do wrong is pretty long. Fabian ___ 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
system hangs during dump + compress usb2-drive
In FreeBSD 8.3 release (possibly in earlier release), dump a file system has 2-3GB or more content can cause system hang in a specific case (pipe to compression): dump FS-on-SATA-drive usb-drive OK dump FS-on-SATA-drive | anyCompress sata-drive OK mv a-large-dump-file from STAT drive to a USB drive OK dump small-FS-on-SATA-drive | anyCompress usb-drive OK small -- 1.8GB or less dump large-FS-on-SATA-drive | anyCompress usb-drive hang content is 3GB or larger (did not try around 2GB yet) When system hangs, no sub system, such video, network, etc, will function. Typically, the unfinished compressed dump file is around 1.5-2.7GB, so guessing dumped file content is close to or over 2GB when failure occurred. Has anyone encountered the same problem? Because this usually takes a few hours to occur, this is hard to watch how/when it happens. Is any way to debug or determine what status the system is? -Jin ___ 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
9.1-RC1 kernel dump - anybody willing to tackle it ?
Hi, here is a kernel dump I got recently: # ls -al /var/crash/ total 285944 drwxr-x--- 2 root wheel512 Sep 5 06:21 . drwxr-xr-x 25 root wheel512 Sep 5 08:30 .. -rw-r--r-- 1 root wheel 2 Sep 5 06:21 bounds -rw--- 1 root wheel 105813 Sep 5 06:21 core.txt.0 -rw--- 1 root wheel449 Sep 5 06:21 info.0 -rw--- 1 root wheel 314290176 Sep 5 06:21 vmcore.0 # cat /var/crash/info.0 Dump header from device /dev/ada0s2b Architecture: i386 Architecture Version: 2 Dump Length: 314290176B (299 MB) Blocksize: 512 Dumptime: Wed Sep 5 06:19:44 2012 Hostname: localhost.localdomain Magic: FreeBSD Kernel Dump Version String: FreeBSD 9.1-RC1 #0: Tue Aug 14 03:56:40 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Panic String: page fault Dump Parity: 3108753009 Bounds: 0 Dump Status: good core.txt.0 : http://pastebin.com/88DEw63T jb ___ 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
Unable to get crash dump
Hi All, Running 8.3-STABLE 5/21/2012 on HP DL360. While testing crash dump functionality, the dump aborts with the following message: Aborting dump due to I/O error. status == 0xb, scsi status == 0x0 ** DUMP FAILED (ERROR 5) ** Automatic reboot in 5 seconds - press a key on the console to abort Googling and searching freebsd.org have produced what appeared to be some what relevant messages, but I found nothing pointing to a cause and fix. I'm hoping someone might be able to point me in a direction to figuring this out. -- Take care Rick Miller ___ 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: OT: Linux EXT4 dump/restore equivalent?
Peter A. Giessel pgies...@mac.com wrote: What I have been completely unable to find is a linux boot disk that has a version of restore that supports ext4. It's unclear to me how a version of restore that supports ext4 would differ from a version of restore that supports UFS. AFAIK restore (unlike dump) is FS-agnostic: it must understand the format of the dumpfile, but it needs no knowledge of how the FS is represented on disk because it uses ordinary system calls (open, write, etc.) to access the FS. What you _do_ need on that recovery disk -- along with a generic restore -- are ext4-aware versions of the kernel, fsck, mkfs, mount, and (arguably) dump. I am very hesitant to use a backup scheme that doesn't have a clear recovery path. +1 ___ 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: OT: Linux EXT4 dump/restore equivalent?
I haven't checked all the features, so I don't know if it includes restore for ext4. According to: http://www.sysresccd.org/Detailed-packages-list It does not contain any version of restore. There are a lot of Linux boot disks out there. I haven't found one yet that includes an ext4 compatible restore. Debian lets you roll your own, but you need to do that before a disaster. It doesn't include useful rescue CDs like FreeBSD does. ___ 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: OT: Linux EXT4 dump/restore equivalent?
Peter A. Giessel pgies...@mac.com responded: According to: http://www.sysresccd.org/Detailed-packages-list It does not contain any version of restore. There are a lot of Linux boot disks out there. I haven't found one yet that includes an ext4 compatible restore. Debian lets you roll your own, but you need to do that before a disaster. It doesn't include useful rescue CDs like FreeBSD does. You could try http://www.sysresccd.org/System-tools Some recovery tools are listed, including FSArchiver and Partimage. Maybe one of those listed recovery tools might fit your need? Tom ___ 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: OT: Linux EXT4 dump/restore equivalent?
On Fri, 29 Jun 2012 00:52:35 -0500, Peter A. Giessel pgies...@mac.com wrote: There are a lot of Linux boot disks out there. I haven't found one yet that includes an ext4 compatible restore. Debian lets you roll your own, but you need to do that before a disaster. It doesn't include useful rescue CDs like FreeBSD does. I've always had great success in the past with RIP Rescue live-cd. It was one of the early live-cds with ext4 support. I wonder if the guy who makes it was smart enough to add restore ___ 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: OT: Linux EXT4 dump/restore equivalent?
On Thu, 28 Jun 2012 20:59:57 +0100, Vincent Hoffman wrote: We use dump to backup ext4 filesystems on linux (Centos6) at work From the linux dump changelog Changes between versions 0.4b41 and 0.4b42 (released June 18, 2009) === 18. Add (preliminary) ext4 support - thanks to libext2fs which does all the job for us. Thanks to Gertjan van Wingerde gwingerde [at] gmail for the patch. Without even trying to start a flamewar, allow me to ask this question: Do they _really_ use file systems over there at Linux land without having an up-to-date dump/restore mechanism for that file systems? I can hardly believe that... Without wishing to bash Linux (I wouldnt be in my job without it,) its man pages are really not very up to date, as the manpage for dump fails to mention this. That's sadly normal. I found the attitude toward documentation in Linux being different from what you would call standard in the rest of UNIX world. Man pages are often out of date (if they ever exist), and pieces of documentation is scattered across the the web, in user pages, wikis, and discussion forums. The concept behind this seems to be: Nobody reads man pages, so we don't write them. I havent used slackware in many years but it used to be my distro of choice until I moved to FreeBSD. Was my first PC Linux, too. :-) On 28/06/2012 20:02, Chris Maness wrote: Is there an equivalent dump/restore ap for a Linux ext4 file system? I am running the latest Slackware, and I would like to make backups like I do for my FreeBSD box. Have you tried the original tools provided by the OS? Do they perform as intended? Maybe do some testing and see if they are sufficient for dealing with ext4. That would be my first impression: Use what's there and see if it works, as it _should_ work (given fundamental UNIX basics). (Sorry, my Linux knowledge is a bit outdated as I don't use it anymore on a regular basis.) -- 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: OT: Linux EXT4 dump/restore equivalent?
On Jun 28, 2012, at 11:59, Vincent Hoffman vi...@unsane.co.uk wrote: We use dump to backup ext4 filesystems on linux (Centos6) at work You can find a version of dump for Linux that supports ext4. What I have been completely unable to find is a linux boot disk that has a version of restore that supports ext4. If anyone knows of one, I would be very interested. I am very hesitant to use a backup scheme that doesn't have a clear recovery path. ___ 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: OT: Linux EXT4 dump/restore equivalent?
On 28/06/2012 21:39, Peter A. Giessel wrote: On Jun 28, 2012, at 11:59, Vincent Hoffman vi...@unsane.co.uk wrote: We use dump to backup ext4 filesystems on linux (Centos6) at work You can find a version of dump for Linux that supports ext4. What I have been completely unable to find is a linux boot disk that has a version of restore that supports ext4. If anyone knows of one, I would be very interested. I am very hesitant to use a backup scheme that doesn't have a clear recovery path. Fair point. I've used the rescue mode on the centos boot CD before, but its not too hard to build a custom centos livecd. I made a pxe bootable version for use at work so we can ssh into it without needing an IP KVM, but I'll try and make a new ISO for you if you like. Vince ___ 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: OT: Linux EXT4 dump/restore equivalent?
On Jun 28, 2012, at 11:59, Vincent Hoffman vi...@unsane.co.uk wrote: We use dump to backup ext4 filesystems on linux (Centos6) at work Peter A. Giessel pgies...@mac.com responded: You can find a version of dump for Linux that supports ext4. What I have been completely unable to find is a linux boot disk that has a version of restore that supports ext4. If anyone knows of one, I would be very interested. I am very hesitant to use a backup scheme that doesn't have a clear recovery path. I've used the System Rescue CD (sysresccd.org), which you can burn to CD or write to USB stick. I haven't checked all the features, so I don't know if it includes restore for ext4. Latest release version is 2.8.0 It ought to read/write ext4. I think it would read (BSD) ffs or ufs v1 but not v2. Tom ___ 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
speed of dump
Another thread, which I seem to have lost, was talking about dump and sizing its cache. Per my promise, appended is the log of this morning's level 0 dump, using C=32. THe system is -CURRENT from March, using AMD Phemon II x4/3ghz and SATA 3gbit drives (one internal, one external.). Robert Huff Backup started. at Mon Jun 11 01:59:00 EDT 2012 /backup clean Disk mounted DUMP: Date of this level 0 dump: Mon Jun 11 01:59:02 2012 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping snapshot of /dev/ad2s1a (/) to 2012.Jun.11.root.dump DUMP: mapping (Pass I) [regular files] DUMP: Cache 32 MB, blocksize = 65536 DUMP: mapping (Pass II) [directories] DUMP: estimated 1295163 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 1295138 tape blocks on 1 volume DUMP: finished in 106 seconds, throughput 12218 KBytes/sec DUMP: level 0 dump on Mon Jun 11 01:59:02 2012 DUMP: Closing 2012.Jun.11.root.dump DUMP: DUMP IS DONE Compressing with gzip ... done DUMP: Date of this level 0 dump: Mon Jun 11 02:02:06 2012 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping snapshot of /dev/ad2s1d (/var) to 2012.Jun.11.var.dump DUMP: mapping (Pass I) [regular files] DUMP: Cache 32 MB, blocksize = 65536 DUMP: mapping (Pass II) [directories] DUMP: estimated 545087 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 545009 tape blocks on 1 volume DUMP: finished in 72 seconds, throughput 7569 KBytes/sec DUMP: level 0 dump on Mon Jun 11 02:02:06 2012 DUMP: Closing 2012.Jun.11.var.dump DUMP: DUMP IS DONE Compressing with gzip... done DUMP: Date of this level 0 dump: Mon Jun 11 02:04:01 2012 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping snapshot of /dev/ad4p2 (/usr) to 2012.Jun.11.usr.dump DUMP: mapping (Pass I) [regular files] DUMP: Cache 32 MB, blocksize = 65536 DUMP: mapping (Pass II) [directories] DUMP: estimated 34156025 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 11.75% done, finished in 0:37 at Mon Jun 11 02:46:45 2012 DUMP: 29.89% done, finished in 0:23 at Mon Jun 11 02:37:39 2012 DUMP: 44.21% done, finished in 0:18 at Mon Jun 11 02:38:07 2012 DUMP: 63.00% done, finished in 0:11 at Mon Jun 11 02:35:56 2012 DUMP: 83.78% done, finished in 0:04 at Mon Jun 11 02:34:02 2012 DUMP: DUMP: 34166302 tape blocks on 1 volume DUMP: finished in 1746 seconds, throughput 19568 KBytes/sec DUMP: level 0 dump on Mon Jun 11 02:04:01 2012 DUMP: Closing 2012.Jun.11.usr.dump DUMP: DUMP IS DONE 569586 /backup/Mon/root 34183010/backup/Mon/usr 139058 /backup/Mon/var 34891656/backup/Mon Disk unmounted. Backup complete. at Mon Jun 11 02:33:30 EDT 2012 ___ 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: speed of dump
On Mon, 11 Jun 2012, Robert Huff wrote: Another thread, which I seem to have lost, was talking about dump and sizing its cache. Per my promise, appended is the log of this morning's level 0 dump, using C=32. THe system is -CURRENT from March, using AMD Phemon II x4/3ghz and SATA 3gbit drives (one internal, one external.). DUMP: finished in 1746 seconds, throughput 19568 KBytes/sec Are you using -b64 ? That can make a serious throughput improvement over smaller values. ___ 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: speed of dump
On Mon, Jun 11, 2012 at 7:14 AM, Robert Huff roberth...@rcn.com wrote: DUMP: finished in 1746 seconds, throughput 19568 KBytes/sec Looks like one of your disks must be USB. -- Adam Vande More ___ 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: speed of dump
Warren Block writes: Another thread, which I seem to have lost, was talking about dump and sizing its cache. Per my promise, appended is the log of this morning's level 0 dump, using C=32. THe system is -CURRENT from March, using AMD Phemon II x4/3ghz and SATA 3gbit drives (one internal, one external.). DUMP: finished in 1746 seconds, throughput 19568 KBytes/sec Are you using -b64 ? That can make a serious throughput improvement over smaller values. No. I'll give it a try. Thanks, Robert Huff ___ 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: speed of dump
Adam Vande More writes: DUMP: finished in 1746 seconds, throughput 19568 KBytes/sec Looks like one of your disks must be USB. Source disk: SATA, I believe 3mbit Target disk: e-SATA, which may be limited to 1.5 mbit/sec. Robert Huff ___ 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
Filesystem dump incremental?
Hello, currently I am experiencing something confusing. Some hours ago I did a level 0 dump with the following command: dump -a -0 -f /mnt/da0/backup-compaq.0.dump / This results in a quite big dump file. After changing a couple of files, I tried to do another dump. This time as level 1. My expectation was that the resulting dump would only contain the files which changed since the level 0 dump. dump -a -1 -f /mnt/da0/backup-compaq.1.dump / To my surprise this seems to generate another full dump instead of incremental. What did I miss or what mistake do I make? The filesystem is mounted with the following options: ufs, local, journaled soft-updates Regards, Matthias ___ 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: Filesystem dump incremental?
On 17/05/2012 12:49, Matthias Petermann wrote: currently I am experiencing something confusing. Some hours ago I did a level 0 dump with the following command: dump -a -0 -f /mnt/da0/backup-compaq.0.dump / This results in a quite big dump file. After changing a couple of files, I tried to do another dump. This time as level 1. My expectation was that the resulting dump would only contain the files which changed since the level 0 dump. dump -a -1 -f /mnt/da0/backup-compaq.1.dump / To my surprise this seems to generate another full dump instead of incremental. What did I miss or what mistake do I make? You need '-u' on tose command lines in order to record the dates of your dumps, including your initial level 0 dump, in /etc/dumpdates. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Filesystem dump incremental?
On Thursday 17 May 2012, Matthias Petermann wrote: dump -a -1 -f /mnt/da0/backup-compaq.1.dump / Try a new full backup with dump -0aLuf /mnt/da0/backup-compaq.1.dump / then for the incremental use dump -1aLuf /mnt/da0/backup-compaq.1.dump / The option you're missing is u, but L is worth using as well when you're backing up a mounted filesystem. You could hack the contents of /etc/dumpdates to avoid having to repeat the level zero dump if you know the date and time when the original one was started. -- 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: Filesystem dump incremental?
Thanks Mike and Matthew, the -u switch was what I missed. It now works fine. Regards, Matthias On 17.05.2012 13:52, Mike Clarke wrote: On Thursday 17 May 2012, Matthias Petermann wrote: dump -a -1 -f /mnt/da0/backup-compaq.1.dump / Try a new full backup with dump -0aLuf /mnt/da0/backup-compaq.1.dump / then for the incremental use dump -1aLuf /mnt/da0/backup-compaq.1.dump / The option you're missing is u, but L is worth using as well when you're backing up a mounted filesystem. You could hack the contents of /etc/dumpdates to avoid having to repeat the level zero dump if you know the date and time when the original one was started. ___ 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 Restore on ZFS root system
I run a ZFS on root FreeBSD system. I know I can backup with snapshots but I want a dump/restore action because I want to transfer this system to a UFS virtual FreeBSD machine. My question is: will dump / (root) make a dump of *ALL* other directories? yanta# df -h Filesystem SizeUsed Avail Capacity Mounted on zroot56G335M 55G 1%/ devfs1.0K1.0K 0B 100%/dev zroot/tmp56G 42M 55G 0%/tmp zroot/usr 60G4.7G 55G 8%/usr zroot/usr/home 58G2.4G 55G 4%/usr/home zroot/usr/ports 56G253M 55G 0%/usr/ports zroot/usr/ports/distfiles56G291M 55G 1% /usr/ports/distfiles zroot/usr/ports/packages 55G 21K 55G 0%/usr/ports/packages zroot/var 56G571M 55G 1%/var zroot/var/crash 55G 23K 55G 0%/var/crash zroot/var/db56G337M 55G 1%/var/db zroot/var/db/pkg55G3.7M 55G 0%/var/db/pkg zroot/var/empty 55G 21K 55G 0%/var/empty zroot/var/log 55G827K 55G 0%/var/log zroot/var/mail 55G 22K 55G 0%/var/mail zroot/var/run 55G 53K 55G 0%/var/run zroot/var/tmp 55G143K 55G 0%/var/tmp devfs 1.0K1.0K 0B 100%/var/named/dev ___ 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 on ZFS root system
On 07/02/2012 11:00, dick wrote: I run a ZFS on root FreeBSD system. I know I can backup with snapshots but I want a dump/restore action because I want to transfer this system to a UFS virtual FreeBSD machine. My question is: will dump / (root) make a dump of *ALL* other directories? Dump works at the filesystem level and will not work on a zfs filesystem [root@banshee /backup/local/zfs]# dump -b 64 -f - ./ dump: ./: unknown file system I'd use tar or cpio or pax or something. On a UFS filesystem dump will only dump the filesystem specified and will not cross mountpoints. Vince yanta# df -h Filesystem SizeUsed Avail Capacity Mounted on zroot56G335M 55G 1%/ devfs1.0K1.0K 0B 100%/dev zroot/tmp56G 42M 55G 0%/tmp zroot/usr 60G4.7G 55G 8%/usr zroot/usr/home 58G2.4G 55G 4%/usr/home zroot/usr/ports 56G253M 55G 0% /usr/ports zroot/usr/ports/distfiles56G291M 55G 1% /usr/ports/distfiles zroot/usr/ports/packages 55G 21K 55G 0% /usr/ports/packages zroot/var 56G571M 55G 1%/var zroot/var/crash 55G 23K 55G 0% /var/crash zroot/var/db56G337M 55G 1%/var/db zroot/var/db/pkg55G3.7M 55G 0%/var/db/pkg zroot/var/empty 55G 21K 55G 0%/var/empty zroot/var/log 55G827K 55G 0% /var/log zroot/var/mail 55G 22K 55G 0% /var/mail zroot/var/run 55G 53K 55G 0% /var/run zroot/var/tmp 55G143K 55G 0%/var/tmp devfs 1.0K1.0K 0B 100%/var/named/dev ___ 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 Restore on ZFS root system
Op 7-2-2012 12:23, Vincent Hoffman schreef: On 07/02/2012 11:00, dick wrote: I run a ZFS on root FreeBSD system. I know I can backup with snapshots but I want a dump/restore action because I want to transfer this system to a UFS virtual FreeBSD machine. My question is: will dump / (root) make a dump of *ALL* other directories? Dump works at the filesystem level and will not work on a zfs filesystem [root@banshee /backup/local/zfs]# dump -b 64 -f - ./ dump: ./: unknown file system I'd use tar or cpio or pax or something. On a UFS filesystem dump will only dump the filesystem specified and will not cross mountpoints. OK, got it. I will have to read up on the best option (tar, cpio or pax) ___ 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 on ZFS root system
On Tue, Feb 7, 2012 at 1:55 PM, dick d...@nagual.nl wrote: Op 7-2-2012 12:23, Vincent Hoffman schreef: On 07/02/2012 11:00, dick wrote: I run a ZFS on root FreeBSD system. I know I can backup with snapshots but I want a dump/restore action because I want to transfer this system to a UFS virtual FreeBSD machine. My question is: will dump / (root) make a dump of *ALL* other directories? Dump works at the filesystem level and will not work on a zfs filesystem [root@banshee /backup/local/zfs]# dump -b 64 -f - ./ dump: ./: unknown file system I'd use tar or cpio or pax or something. On a UFS filesystem dump will only dump the filesystem specified and will not cross mountpoints. OK, got it. I will have to read up on the best option (tar, cpio or pax) You can always clone it using zfs send / receive to your vm: http://www.aisecure.net/2011/03/26/cloning-a-zfs-bootable-system/ -- George Kontostanos Aicom telecoms ltd http://www.aisecure.net ___ 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 on ZFS root system
On 07/02/2012, at 22:25, dick wrote: Op 7-2-2012 12:23, Vincent Hoffman schreef: On 07/02/2012 11:00, dick wrote: I run a ZFS on root FreeBSD system. I know I can backup with snapshots but I want a dump/restore action because I want to transfer this system to a UFS virtual FreeBSD machine. My question is: will dump / (root) make a dump of *ALL* other directories? Dump works at the filesystem level and will not work on a zfs filesystem [root@banshee /backup/local/zfs]# dump -b 64 -f - ./ dump: ./: unknown file system I'd use tar or cpio or pax or something. On a UFS filesystem dump will only dump the filesystem specified and will not cross mountpoints. OK, got it. I will have to read up on the best option (tar, cpio or pax) ___ 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 Why not use the ZFS send / receive command? Sincerely, William Brown Research Teaching, Technology Services The University of Adelaide, AUSTRALIA 5005 CRICOS Provider Number 00123M - IMPORTANT: This message may contain confidential or legally privileged information. If you think it was sent to you by mistake, please delete all copies and advise the sender. For the purposes of the SPAM Act 2003, this email is authorised by The University of Adelaide. pgp.mit.edu http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x3C0AC6DAB2F928A2 signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Dump Restore on ZFS root system
On Tue, 7 Feb 2012, dick wrote: Op 7-2-2012 12:23, Vincent Hoffman schreef: On 07/02/2012 11:00, dick wrote: I run a ZFS on root FreeBSD system. I know I can backup with snapshots but I want a dump/restore action because I want to transfer this system to a UFS virtual FreeBSD machine. My question is: will dump / (root) make a dump of *ALL* other directories? Dump works at the filesystem level and will not work on a zfs filesystem [root@banshee /backup/local/zfs]# dump -b 64 -f - ./ dump: ./: unknown file system I'd use tar or cpio or pax or something. On a UFS filesystem dump will only dump the filesystem specified and will not cross mountpoints. OK, got it. I will have to read up on the best option (tar, cpio or pax) Or rsync, with -a, -H, and probably some other options I can't recall. ___ 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: non-responsive FreeBSD-9.0 after dump command
Le Wed, 18 Jan 2012 16:42:10 -0700, Dale Scott dalesc...@shaw.ca a écrit : # mount /dev/ada0p2 on / (ufs, local, journaled soft-updates) devfs on /dev (devfs, local, multilabel) /dev/ad1as1d on /backup (ufs, local, soft-updates) # # cd /backup # dump -0aLf 20120118.dump / There is no output after hitting enter, and afterwards the system is generally unresponsive. A command (e.g., whoami) typed into the VirtualBox server console and an ssh terminal is echo'd, but that's all. I had started top in a seperate ssh terminal before issuing the dump command, and it shows mksnap_ffs running with 98%-100% WCPU for about 55 minutes, at which point top stops updating. I gave up after 70 minutes and yanked the virtual power cord. There are several reports that snapshots are broken on ufs+SUJ and dump takes a snapshot. Regards. ___ 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
non-responsive FreeBSD-9.0 after dump command
I'm getting a non-responsive system after issuing dump on a relatively fresh install of FreeBSD-9.0-RELEASE. The system is a VirtualBox 4.1.2 vm, with a 20GB GPT system drive and a 20GB MBR backup drive. Since it was created, the ports tree has been updated and apache22, mysql55-server and python/django installed (and a number of minor utilities). Everything seems to work ok, except for dump: # mount /dev/ada0p2 on / (ufs, local, journaled soft-updates) devfs on /dev (devfs, local, multilabel) /dev/ad1as1d on /backup (ufs, local, soft-updates) # # cd /backup # dump -0aLf 20120118.dump / There is no output after hitting enter, and afterwards the system is generally unresponsive. A command (e.g., whoami) typed into the VirtualBox server console and an ssh terminal is echo'd, but that's all. I had started top in a seperate ssh terminal before issuing the dump command, and it shows mksnap_ffs running with 98%-100% WCPU for about 55 minutes, at which point top stops updating. I gave up after 70 minutes and yanked the virtual power cord. I then created a new FBSD-9.0 VM (system install from dvd only, and also create/fdisk/label/mount a new virtual backup drive). On this vm, dump works as expected! I moved the virtual backup drive from new to old, and also re-partitioned/re-labled the backup drive on the problem system, but no effect. FWIW, fdisk reports that on both system disks (non-working and working), the chunks do not start on track boundaries (I used auto installing the systems). Does any of this make any sense to anyone? Any ideas on how to correct the situation? I don't mind re-configure the new vm like the old, but not knowing what went wrong concerns me (and if it's just going to happen again). My basic intent is to get version 2 of a live server working first as a vm, then restore a dump onto real hardware. Thanks in advance for any and all assistance, Dale - Transparency with Trust http://www.dalescott.net ___ 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
Need to Backup Using Dump
I have two FreeBSD 8.2-STABLE servers running NFS. I have tons of files on Server A that I want to backup to a big drive on Sever B. Server B nfs_mounts one of the filesystems on Server A to /mnt. So if I wanted to make a backup of the filesytem on Server A to Server B I tried: dump -d /home/my_home/backups/20111024 /mnt but each time I try this it tells me that filesystem /mnt is unknown. /mnt is not in /etc/fstab. I manually mounted this via NFS and that's where all the files I want to backup are accessible to the command line on Server B. What am I missing? ___ 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: Need to Backup Using Dump
El día Sunday, October 23, 2011 a las 06:04:14AM -0700, Bill Tillman escribió: I have two FreeBSD 8.2-STABLE servers running NFS. I have tons of files on Server A that I want to backup to a big drive on Sever B. Server B nfs_mounts one of the filesystems on Server A to /mnt. So if I wanted to make a backup of the filesytem on Server A to Server B I tried: dump -d /home/my_home/backups/20111024 /mnt but each time I try this it tells me that filesystem /mnt is unknown. /mnt is not in /etc/fstab. I manually mounted this via NFS and that's where all the files I want to backup are accessible to the command line on Server B. What am I missing? Following dump(8) the file system to be dumped must be a device special file or its mountpoint from fstab(5). HIH 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/ 200†-20††: 10 años de guerra en Afghanistan. ¡Basta ya! 200†-20††: 10 years war in Afghanistan. Stop it now! 200†-20††: 10 Jahre Krieg in Afghanistan. Schluss jetzt endlich! ___ 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: Need to Backup Using Dump
On Sun, 23 Oct 2011, Bill Tillman wrote: I have two FreeBSD 8.2-STABLE servers running NFS. I have tons of files on Server A that I want to backup to a big drive on Sever B. Server B nfs_mounts one of the filesystems on Server A to /mnt. So if I wanted to make a backup of the filesytem on Server A to Server B I tried: dump -d /home/my_home/backups/20111024 /mnt but each time I try this it tells me that filesystem /mnt is unknown. /mnt is not in /etc/fstab. I manually mounted this via NFS and that's where all the files I want to backup are accessible to the command line on Server B. What am I missing? dump(8) works on entire filesystems. To copy directories, consider rsync. To copy directories but put them into archives, there's tar and numerous others. ___ 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: Need to Backup Using Dump
On Sun, 23 Oct 2011 06:04:14 -0700 (PDT), Bill Tillman wrote: I have two FreeBSD 8.2-STABLE servers running NFS. I have tons of files on Server A that I want to backup to a big drive on Sever B. Server B nfs_mounts one of the filesystems on Server A to /mnt. So if I wanted to make a backup of the filesytem on Server A to Server B I tried: dump -d /home/my_home/backups/20111024 /mnt but each time I try this it tells me that filesystem /mnt is unknown. /mnt is not in /etc/fstab. I manually mounted this via NFS and that's where all the files I want to backup are accessible to the command line on Server B. What am I missing? The dump + restore mechanism operates on device files representing a file system, not a _mounted_ file system, as source. If, for example, your /home partition is /dev/ad0s1e, and you've mounted the target at /mnt, then you could do: # cd /mnt # dump -0 -f - /dev/ad0s1e | restore -r -f - Therefore /home has to be unmounted (or add flag -L to dump from mounted file systems). But note that this will dump the _complete_ file system's content to /mnt as dump cannot be more selective here. An alternative is to use rsync or cpdup where you can explicitely address a subtree to be copied instead of the whole file system. -- 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: Need to Backup Using Dump
Hello. 2011/10/23 21:08:14 +0200 Polytropon free...@edvax.de = To Bill Tillman : P The dump + restore mechanism operates on device files P representing a file system, not a _mounted_ file system, P as source. dump(8) is able to make a snapshot behind teh scenes, and use that snapshot as a source for dump: -L This option is to notify dump that it is dumping a live file sys tem. To obtain a consistent dump image, dump takes a snapshot of the file system in the .snap directory in the root of the file system being dumped and then does a dump of the snapshot. -- Peter Vereshagin pe...@vereshagin.org (http://vereshagin.org) pgp: A0E26627 ___ 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: Need to Backup Using Dump
On Sun, 23 Oct 2011, Polytropon wrote: But note that this will dump the _complete_ file system's content to /mnt as dump cannot be more selective here. The nodump flag along with -h0 can be used to exclude files or directories. But agreed, dump is gear towards entire filesystems. ___ 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, how to reduce slice size
# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad4s1a 2G206M1.6G11%/ devfs 1.0k1.0k 0B 100%/dev /dev/ad4s1e3.9G 13M3.6G 0%/tmp /dev/ad4s1f 40G 25G 12G67%/usr /dev/ad4s1d 31G3.6G 24G13%/var procfs 4.0k4.0k 0B 100%/proc /dev/ad2s1f 39G 25G 10G71%/mnt devfs 1.0k1.0k 0B 100%/var/named/dev as you can see /dev/ad4s1f is 40G and /dev/ad2s1f is 39G but on ad4s1f only 25G used. How can I dump /dev/ad4s1f and restore it on /dev/ad2s1f? You can't. ad4s1f has 25G of files, but ad2s1f only has 10G of free space. You need a bigger disk. If you're just moving things around, I agree that a $100 USB disk is the best way to store backups temporarily. R's, 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: dump/restore, how to reduce slice size
On Fri, Sep 30, 2011 at 03:41:26PM +0200, Damien Fleuriot wrote: On 9/29/11 10:09 PM, Jerry McAllister wrote: On Thu, Sep 29, 2011 at 10:36:38PM +0300, ??? ??? wrote: Hi, Freebsd-questions. # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad4s1a 2G206M1.6G11%/ devfs 1.0k1.0k 0B 100%/dev /dev/ad4s1e3.9G 13M3.6G 0%/tmp /dev/ad4s1f 40G 25G 12G67%/usr /dev/ad4s1d 31G3.6G 24G13%/var procfs 4.0k4.0k 0B 100%/proc /dev/ad2s1f 39G 25G 10G71%/mnt devfs 1.0k1.0k 0B 100%/var/named/dev as you can see /dev/ad4s1f is 40G and /dev/ad2s1f is 39G but on ad4s1f only 25G used. How can I dump /dev/ad4s1f and restore it on /dev/ad2s1f? These commands: #mount /dev/ad2s1f /mnt #cd /mnt #dump -0Lf - /usr | restore -rf - does not help, because of ad2s1f does not have space to restore 'end of ' /dev/ad4s1f. May help any? Well, you are going to have difficulty putting 50 GB on a 39 GB partition. (25GB + 25GB = 50GB). It won't work. You could try compressing the dump, but dump files do not tend to compress well and even if you got a 50% compression, you would still be really close to overfill. Probably you need to go to the store and get a nice big USB drive and slice and partition it in to a bunch of 50 GB partitions and pipe your dump to a restore in those partitions on that drive. You can round-robin your backups to those USB partitions. My backup to a USB hard drive just saved me the beginning of this week when the old machine died of heat prostration. Dump is supposed to take only the used space. Yes. He already has 25 GB used on the partition and wants to add another approx 25 GB in a 39 GB partition. There ain't room. jerry @OP, refer the following link for correct dump/restore syntax: http://www.wonkity.com/~wblock/docs/html/backup.html#_tt_dump_tt_with_compression ___ 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[2]: dump/restore, how to reduce slice size
Здравствуйте, Robert. Вы писали 30 сентября 2011 г., 4:11:15: From owner-freebsd-questi...@freebsd.org Thu Sep 29 14:37:35 2011 Date: Thu, 29 Sep 2011 22:36:38 +0300 From: =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= kes-...@yandex.ru To: freebsd-questions@freebsd.org Subject: dump/restore, how to reduce slice size Hi, Freebsd-questions. # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad4s1a 2G206M1.6G11%/ devfs 1.0k1.0k 0B 100%/dev /dev/ad4s1e3.9G 13M3.6G 0%/tmp /dev/ad4s1f 40G 25G 12G67%/usr /dev/ad4s1d 31G3.6G 24G13%/var procfs 4.0k4.0k 0B 100%/proc /dev/ad2s1f 39G 25G 10G71%/mnt devfs 1.0k1.0k 0B 100%/var/named/dev as you can see /dev/ad4s1f is 40G and /dev/ad2s1f is 39G but on ad4s1f only 25G used. How can I dump /dev/ad4s1f and restore it on /dev/ad2s1f? These commands: #mount /dev/ad2s1f /mnt #cd /mnt #dump -0Lf - /usr | restore -rf - does not help, because of ad2s1f does not have space to restore 'end of ' /dev/ad4s1f. May help any? RB ad2s1f already has 25 gigs of stuff on it. with ounly 14 gigs 'free'. RB ad4s1f has 25 gigs of stuff on _it_. RB The 25 gigs of ad4s1f will not fit in the 14 gigs of free space on RB ad2s1f. It is state after restoration. Before that I do the prestine file system with: newfs /dev/ad2s1f mount /dev/ad2s1f /mnt cd /mnt dump -0Lf - /usr | restore -rf - at the end of restore process I got error about that on target file system there is no inode . abourt? [yn] I type 'n'. there are about 10 inodes missed. when I compare files it seems that are same on source and target. Is that Ok, may I do not worry about that error messages? RB Now, RB *IF* the existing 'stuff' on ad2s1f is of no value, and the -only- thing RB you want to have on that filesystem is the 'copy' of ad4s1f, RB *THEN* there is 'simple' solution. You need to delete the files on RB ad4s1f -before- trying the dump/restor. In the commnds you show, above, RB fter the 'cd /mnt', and before the dump/restore, Type in 'rm -fr /mnt/*', RB but DO NOT hit the enter key. Look at what you typed, and make sure RB that there is no white-spce immediately before the '*'. Double check RB that there is no whitespce after the first '/'. or before the 2nd one. RB TRIPLE CHECK that there are no spaces before the '*'. Have you made RB a full back-up of the system recently? If not, abort this commqnd, and RB make the full backup before trying this again. RB *IF* you are absolutely certain you have typed the commnd correctly, _and_ RB you have current full-system backup, then go ahead nd press the enter RB key. thank you for attention. I understand that. RB As my friend Dante Brown once remarked: RB All hope abandon RB ye who press Enter RB here. -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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/restore, how to reduce slice size
Hi, Freebsd-questions. # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad4s1a 2G206M1.6G11%/ devfs 1.0k1.0k 0B 100%/dev /dev/ad4s1e3.9G 13M3.6G 0%/tmp /dev/ad4s1f 40G 25G 12G67%/usr /dev/ad4s1d 31G3.6G 24G13%/var procfs 4.0k4.0k 0B 100%/proc /dev/ad2s1f 39G 25G 10G71%/mnt devfs 1.0k1.0k 0B 100%/var/named/dev as you can see /dev/ad4s1f is 40G and /dev/ad2s1f is 39G but on ad4s1f only 25G used. How can I dump /dev/ad4s1f and restore it on /dev/ad2s1f? These commands: #mount /dev/ad2s1f /mnt #cd /mnt #dump -0Lf - /usr | restore -rf - does not help, because of ad2s1f does not have space to restore 'end of ' /dev/ad4s1f. May help any? -- Konkov mailto:kes-...@yandex.ru ___ 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, how to reduce slice size
On Thu, Sep 29, 2011 at 10:36:38PM +0300, ??? ??? wrote: Hi, Freebsd-questions. # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad4s1a 2G206M1.6G11%/ devfs 1.0k1.0k 0B 100%/dev /dev/ad4s1e3.9G 13M3.6G 0%/tmp /dev/ad4s1f 40G 25G 12G67%/usr /dev/ad4s1d 31G3.6G 24G13%/var procfs 4.0k4.0k 0B 100%/proc /dev/ad2s1f 39G 25G 10G71%/mnt devfs 1.0k1.0k 0B 100%/var/named/dev as you can see /dev/ad4s1f is 40G and /dev/ad2s1f is 39G but on ad4s1f only 25G used. How can I dump /dev/ad4s1f and restore it on /dev/ad2s1f? These commands: #mount /dev/ad2s1f /mnt #cd /mnt #dump -0Lf - /usr | restore -rf - does not help, because of ad2s1f does not have space to restore 'end of ' /dev/ad4s1f. May help any? Well, you are going to have difficulty putting 50 GB on a 39 GB partition. (25GB + 25GB = 50GB). It won't work. You could try compressing the dump, but dump files do not tend to compress well and even if you got a 50% compression, you would still be really close to overfill. Probably you need to go to the store and get a nice big USB drive and slice and partition it in to a bunch of 50 GB partitions and pipe your dump to a restore in those partitions on that drive. You can round-robin your backups to those USB partitions. My backup to a USB hard drive just saved me the beginning of this week when the old machine died of heat prostration. jerry jerry -- Konkov mailto:kes-...@yandex.ru ___ 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: Help with crash dump
2011-09-08 22:11, Andrea Venturoli skrev: Hello. Anyone can give any hint on this? Guessing! You have run out of swapspace, based on these 2 lines panic: ffs_write: dir write current process = 0 (swapper) Or you have a hardware error. Does the current process change between panics or is it always the same? I'm in no sense a kernel debugger, but it's a hint. I really have no clue. bye Thanks av. # uname -a FreeBSD x..it 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4 #1: Wed Dec 15 11:53:13 CET 2010 r...@x..it:/usr/obj/usr/src/sys/x i386 # kgdb kernel.debug /var/crash/vmcore.17 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Unread portion of the kernel message buffer: panic: ffs_write: dir write cpuid = 3 Uptime: 26d9h4m27s Physical memory: 2033 MB Dumping 300 MB: 285 269 253 237 221 205 189 173 157 141 125 109 93 77kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x20:0xc059accb stack pointer = 0x28:0xc0c20ccc frame pointer = 0x28:0xc0c20cec code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 0 (swapper) trap number = 12 panic: page fault cpuid = 3 61 45 29 13 Reading symbols from /boot/kernel/splash_bmp.ko...Reading symbols from /boot/kernel/splash_bmp.ko.symbols...done. done. Loaded symbols for /boot/kernel/splash_bmp.ko Reading symbols from /boot/kernel/geom_stripe.ko...Reading symbols from /boot/kernel/geom_stripe.ko.symbols...done. done. Loaded symbols for /boot/kernel/geom_stripe.ko Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko #0 doadump () at pcpu.h:196 196 __asm __volatile(movl %%fs:0,%0 : =r (td)); (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc0563d48 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc0564025 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc06cd16d in ffs_write (ap=0xe6912a44) at /usr/src/sys/ufs/ffs/ffs_vnops.c:667 #4 0xc0740640 in VOP_WRITE_APV (vop=0xc07ba4e0, a=0xe6912a44) at vnode_if.c:691 #5 0xc06fd8d6 in vnode_pager_generic_putpages (vp=0xc672f678, m=0xe6912bb0, bytecount=Variable bytecount is not available. ) at vnode_if.h:373 #6 0xc05d4a5f in vop_stdputpages (ap=0xe6912ad4) at /usr/src/sys/kern/vfs_default.c:540 #7 0xc073faf3 in VOP_PUTPAGES_APV (vop=0xc07ba4e0, a=0xe6912ad4) at vnode_if.c:2189 #8 0xc06fda5f in vnode_pager_putpages (object=0xcb14ac80, m=0xe6912bb0, count=1, sync=0, rtvals=0xe6912b20) at vnode_if.h:1164 #9 0xc06f730b in vm_pageout_flush (mc=0xe6912bb0, count=1, flags=0) at vm_pager.h:148 #10 0xc06f7661 in vm_pageout_clean (m=Variable m is not available. ) at /usr/src/sys/vm/vm_pageout.c:403 #11 0xc06f92a2 in vm_pageout () at /usr/src/sys/vm/vm_pageout.c:1017 #12 0xc053e9a1 in fork_exit (callout=0xc06f82d6 vm_pageout, arg=0x0, frame=0xe6912d38) at /usr/src/sys/kern/kern_fork.c:811 #13 0xc0718b30 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:271 (kgdb) ___ 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
