Re: 3.1.1 zfs-snapshot error
On Fri, Jul 23, 2010 at 4:18 PM, Brian Cuttler br...@wadsworth.org wrote: I'm dumping core on an Solaris 10x86 amanda client when I use dumptype zfs-snapshot. Is tar dumping core, or an Amanda app? I recall we had a bug discussed here where gnutar would segfault while working on ZFS snapshots due to the funny behavior of the .zfs directory. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: 3.1.1 zfs-snapshot error
Dustin, On Fri, Jul 23, 2010 at 04:24:27PM -0400, Dustin J. Mitchell wrote: On Fri, Jul 23, 2010 at 4:18 PM, Brian Cuttler br...@wadsworth.org wrote: I'm dumping core on an Solaris 10x86 amanda client when I use dumptype zfs-snapshot. Is tar dumping core, or an Amanda app? I recall we had a bug discussed here where gnutar would segfault while working on ZFS snapshots due to the funny behavior of the .zfs directory. I think its an amanda app. Just running amcheck I'm ok when the DLE specifies comp-user-tar, but dump core in /tmp/amanda when I specify zfs-snapshot. I have yet to run an actual dump on the new client and at the mement only one of the 4 DLEs contains any data, (/ does, the user partitions do not). I think this is about as much as I can give you without sending the core files. Nothing about the debug file catches my eye, but I don't know if that is a surprise. thank you, Brian server side --- amcheck -c flower bioxrs /rpool1/samba/cms2 Amanda Backup Client Hosts Check ERROR: bioxrs: Script 'amzfs-snapshot' command 'PRE-DLE-AMCHECK' terminated with signal 11: see /tmp/amanda/client/flower/selfcheck.20100723163420.debug ERROR: bioxrs: Script 'amzfs-snapshot' command 'POST-DLE-AMCHECK' terminated with signal 11: see /tmp/amanda/client/flower/selfcheck.20100723163420.debug Client check: 1 host checked in 11.978 seconds. 2 problems found. (brought to you by Amanda 2.6.1p1) client side --- # ls -R .: amandad clientcore core20100723 ./amandad: amandad.20100723163414.debug ./client: flower ./client/flower: amgtar.20100723163423.debug Amzfs_snapshot.20100723163423.debug amgtar.20100723163423000.debug selfcheck.20100723163420.debug Amzfs_snapshot.20100723163420.debug # cat /tmp/amanda/client/flower/selfcheck.20100723163420.debug Fri Jul 23 16:34:20 2010: selfcheck: pid 14922 ruid 110 euid 110 version 3.1.1: start at Fri Jul 23 16:34:20 2010 Fri Jul 23 16:34:20 2010: selfcheck: version 3.1.1 Fri Jul 23 16:34:20 2010: selfcheck: pid 14922 ruid 110 euid 110 version 3.1.1: rename at Fri Jul 23 16:34:20 2010 Fri Jul 23 16:34:20 2010: selfcheck: Spawning /usr/local/libexec/amanda/application/amzfs-snapshot amzfs-snapshot PRE-DLE-AMCHECK --execute-where client --config flower --host bioxrs --disk /rpool1/samba/cms2 --device /rpool1/samba/cms2 --df-path /usr/sbin/df --pfexec YES --pfexec-path /usr/bin/pfexec --zfs-path /usr/sbin/zfs in pipeline Fri Jul 23 16:34:23 2010: selfcheck: checking disk /rpool1/samba/cms2 Fri Jul 23 16:34:23 2010: selfcheck: Spawning /usr/local/libexec/amanda/application/amgtar amgtar support --config flower --host bioxrs --disk /rpool1/samba/cms2 --device /rpool1/samba/cms2 in pipeline Fri Jul 23 16:34:23 2010: selfcheck: support line: CONFIG YES Fri Jul 23 16:34:23 2010: selfcheck: support line: HOST YES Fri Jul 23 16:34:23 2010: selfcheck: support line: DISK YES Fri Jul 23 16:34:23 2010: selfcheck: support line: MAX-LEVEL 399 Fri Jul 23 16:34:23 2010: selfcheck: support line: INDEX-LINE YES Fri Jul 23 16:34:23 2010: selfcheck: support line: INDEX-XML NO Fri Jul 23 16:34:23 2010: selfcheck: support line: MESSAGE-LINE YES Fri Jul 23 16:34:23 2010: selfcheck: support line: MESSAGE-XML NO Fri Jul 23 16:34:23 2010: selfcheck: support line: RECORD YES Fri Jul 23 16:34:23 2010: selfcheck: support line: INCLUDE-FILE YES Fri Jul 23 16:34:23 2010: selfcheck: support line: INCLUDE-LIST YES Fri Jul 23 16:34:23 2010: selfcheck: support line: INCLUDE-LIST-GLOB YES Fri Jul 23 16:34:23 2010: selfcheck: support line: INCLUDE-OPTIONAL YES Fri Jul 23 16:34:23 2010: selfcheck: support line: EXCLUDE-FILE YES Fri Jul 23 16:34:23 2010: selfcheck: support line: EXCLUDE-LIST YES Fri Jul 23 16:34:23 2010: selfcheck: support line: EXCLUDE-LIST-GLOB YES Fri Jul 23 16:34:23 2010: selfcheck: support line: EXCLUDE-OPTIONAL YES Fri Jul 23 16:34:23 2010: selfcheck: support line: COLLECTION NO Fri Jul 23 16:34:23 2010: selfcheck: support line: MULTI-ESTIMATE YES Fri Jul 23 16:34:23 2010: selfcheck: support line: CALCSIZE YES Fri Jul 23 16:34:23 2010: selfcheck: support line: CLIENT-ESTIMATE YES Fri Jul 23 16:34:23 2010: selfcheck: Spawning /usr/local/libexec/amanda/application/amgtar amgtar selfcheck --message line --config flower --host bioxrs --disk /rpool1/samba/cms2 --device /rpool1/samba/cms2 --index line --record --atime-preserve no in pipeline Fri Jul 23 16:34:23 2010: selfcheck: Spawning /usr/local/libexec/amanda/application/amzfs-snapshot amzfs-snapshot POST-DLE-AMCHECK --execute-where client --config flower --host bioxrs --disk /rpool1/samba/cms2 --device /rpool1/samba/cms2 --df-path /usr/sbin/df --pfexec YES --pfexec-path /usr/bin/pfexec --zfs-path /usr/sbin/zfs in pipeline Fri Jul 23 16:34:25 2010: selfcheck: pid 14922 finish time Fri Jul 23 16:34:25 2010 Dustin --
RE: 3.1.1 zfs-snapshot error
We are also running Solaris 10 x86 zfs. I am wondering if you are seeing the same problem. From what I read the zfs_snapshot api call amgtar. There is a bug in gtar in how it handles .zfs 1) Search the zmanda archive for runtar error that I do not understand 2) Look at the bug reported to gtar group http://lists.gnu.org/archive/html/bug-tar/2010-07/msg00035.html that Chapman Flack reported. If this is it I can tell you how I haved resolved the problem until gtar gets patched. Robert -Original Message- From: owner-amanda-us...@amanda.org [mailto:owner-amanda- us...@amanda.org] On Behalf Of Brian Cuttler Sent: Friday, July 23, 2010 4:18 PM To: dus...@zmanda.org Cc: amanda-users@amanda.org; Chris Knight; Dave Remling Subject: 3.1.1 zfs-snapshot error Dustin, I'm dumping core on an Solaris 10x86 amanda client when I use dumptype zfs-snapshot. Seems ok (means it passed amcheck) when specifying a tar dump without snapshots, but actually dumps core in /tmp/amanda when zfs-snapshot dumptype is specified in the disklist. I thing the server, also Solaris 10x86 but version 2.6.1p1 is configured correctly because it has other DLE, not on the 3.1.1 client, that use zfs-snapshot without error. I can reproduce and send files, including if you want them the core files. thanks, Brian --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: 3.1.1 zfs-snapshot error
Robert, Thanks - will see about that on monday, but this is not a new process for us, just another client, we have been using zfs-snapshots for, I forget how long. Maybe I'll try, now that I the pre-reqs installed, installing my 2.6.1p1 client and see if I can differentiate that way. We where ok on all other systems, it just seem to be in the amanda 3.1.1 client side of things. good weekend, Brian On Fri, Jul 23, 2010 at 05:00:26PM -0400, McGraw, Robert P wrote: We are also running Solaris 10 x86 zfs. I am wondering if you are seeing the same problem. From what I read the zfs_snapshot api call amgtar. There is a bug in gtar in how it handles .zfs 1) Search the zmanda archive for runtar error that I do not understand 2) Look at the bug reported to gtar group http://lists.gnu.org/archive/html/bug-tar/2010-07/msg00035.html that Chapman Flack reported. If this is it I can tell you how I haved resolved the problem until gtar gets patched. Robert -Original Message- From: owner-amanda-us...@amanda.org [mailto:owner-amanda- us...@amanda.org] On Behalf Of Brian Cuttler Sent: Friday, July 23, 2010 4:18 PM To: dus...@zmanda.org Cc: amanda-users@amanda.org; Chris Knight; Dave Remling Subject: 3.1.1 zfs-snapshot error Dustin, I'm dumping core on an Solaris 10x86 amanda client when I use dumptype zfs-snapshot. Seems ok (means it passed amcheck) when specifying a tar dump without snapshots, but actually dumps core in /tmp/amanda when zfs-snapshot dumptype is specified in the disklist. I thing the server, also Solaris 10x86 but version 2.6.1p1 is configured correctly because it has other DLE, not on the 3.1.1 client, that use zfs-snapshot without error. I can reproduce and send files, including if you want them the core files. thanks, Brian --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
