Re: checking date of file to be dumped
Am 04.06.2013 16:37, schrieb Jon LaBadie: Probably not what you are looking for, but you could use smbclient to do a dos dir command on the file. $ smbclient -N -c 'dir ifconfig-mumsxp /t:c' //cyberxp/jon Domain=[CYBERXP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] ifconfig-mumsxpA 933 Mon Feb 21 18:55:46 2011 51199 blocks of size 2097152. 35262 blocks available $ The /t:c option causes create timestamp to be printed. Of course you still have to get rid of headers etc. Thanks for the suggestion, Jon ... gotta try that ... Stefan
amanda 3.3.3 too many files
Hello amanda users, I just updates amanda 3.3.0 to 3.3.0 on a Solaris 10/x86 system. The system is both the server and the client, there are no other clients of this system. We have ~265 DLEs on this system (large zfs arrays and all samba shares are their own file systems and DLE, thank goodness I was able to talk my manager out of making all user directories their own DLE as well, though they are their own zfs file systems). The following errors are -not- new with 3.3.3, we've had them for a while, I'd hoped the upgrade would take are of it. Also the amcheck leaves an amanda-check file around for one of the zfs file systems (yes, configured to use zfs snapshot). [I'm pretty sure these two errors are related to one another] The filesystem amanda-*-check file left is for the same filesystem each night, unless we add/remove DLE/filesystems. So I think it is the nth filesystem and at the limit of the open file counter, rather than something in the file system itself. I was hoping there was an easy fix for this. Last I recall on the topic it had to do with the fillm being a 32 bit rather than 64 bit value (I could be wrong about this). Otherwise all # amcheck tests run successfully. Will run # amdump this evening but do not anticipate any issues there. thank you, Brian amcheck -c finsen Amanda Backup Client Hosts Check ERROR: finsen: service selfcheck: selfcheck: Error opening pipe to child: Too many open files ERROR: finsen: service /usr/local/libexec/amanda/selfcheck failed: pid 8590 exited with code 1 Client check: 1 host checked in 83.304 seconds. 2 problems found. (brought to you by Amanda 3.3.3) from /var/log/conlog Jun 5 10:55:04 finsen amandad[8583]: [ID 927837 daemon.info] connect from finsen.wadsworth.org Jun 5 10:56:27 finsen selfcheck[8590]: [ID 702911 daemon.error] Error opening pipe to child: Too many open files --- 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
Re: amanda 3.3.3 too many files
Brian, Can you increase the number of open files at the system level? amcheck check all DLEs in parallel, you can try to add spindle (in the disklist) to reduce parallelism but that can have a bad impact on dump performance, so it is not a good workaround. You would like a maxcheck setting similar to maxdump, I put it in my TODO list. Jean-Louis On 06/05/2013 11:05 AM, Brian Cuttler wrote: Hello amanda users, I just updates amanda 3.3.0 to 3.3.0 on a Solaris 10/x86 system. The system is both the server and the client, there are no other clients of this system. We have ~265 DLEs on this system (large zfs arrays and all samba shares are their own file systems and DLE, thank goodness I was able to talk my manager out of making all user directories their own DLE as well, though they are their own zfs file systems). The following errors are -not- new with 3.3.3, we've had them for a while, I'd hoped the upgrade would take are of it. Also the amcheck leaves an amanda-check file around for one of the zfs file systems (yes, configured to use zfs snapshot). [I'm pretty sure these two errors are related to one another] The filesystem amanda-*-check file left is for the same filesystem each night, unless we add/remove DLE/filesystems. So I think it is the nth filesystem and at the limit of the open file counter, rather than something in the file system itself. I was hoping there was an easy fix for this. Last I recall on the topic it had to do with the fillm being a 32 bit rather than 64 bit value (I could be wrong about this). Otherwise all # amcheck tests run successfully. Will run # amdump this evening but do not anticipate any issues there. thank you, Brian amcheck -c finsen Amanda Backup Client Hosts Check ERROR: finsen: service selfcheck: selfcheck: Error opening pipe to child: Too many open files ERROR: finsen: service /usr/local/libexec/amanda/selfcheck failed: pid 8590 exited with code 1 Client check: 1 host checked in 83.304 seconds. 2 problems found. (brought to you by Amanda 3.3.3) from /var/log/conlog Jun 5 10:55:04 finsen amandad[8583]: [ID 927837 daemon.info] connect from finsen.wadsworth.org Jun 5 10:56:27 finsen selfcheck[8590]: [ID 702911 daemon.error] Error opening pipe to child: Too many open files --- 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
Re: amanda 3.3.3 too many files
On Wed, Jun 05, 2013 at 11:05:36AM -0400, Brian Cuttler wrote: Hello amanda users, I just updates amanda 3.3.0 to 3.3.0 on a Solaris 10/x86 system. The system is both the server and the client, there are no other clients of this system. We have ~265 DLEs on this system (large zfs arrays and all samba shares are their own file systems and DLE, thank goodness I was able to talk my manager out of making all user directories their own DLE as well, though they are their own zfs file systems). The following errors are -not- new with 3.3.3, we've had them for a while, I'd hoped the upgrade would take are of it. Also the amcheck leaves an amanda-check file around for one of the zfs file systems (yes, configured to use zfs snapshot). [I'm pretty sure these two errors are related to one another] The filesystem amanda-*-check file left is for the same filesystem each night, unless we add/remove DLE/filesystems. So I think it is the nth filesystem and at the limit of the open file counter, rather than something in the file system itself. I was hoping there was an easy fix for this. Last I recall on the topic it had to do with the fillm being a 32 bit rather than 64 bit value (I could be wrong about this). It could very well be too many files open. My research says Solaris 10 default value for process.max-file-descriptor is 256. Check it with ulimit -n. Solaris maintains both a soft and a hard set of limits for some parameters. To check the hard limit try ulimit -H -n. For process.max-file-descriptor an ordinary user can reduce the hard limit but not increase it. That user can also reduce the soft limit and can raise it to a maximum of the hard limit. To raise the soft limit try either: ulimit -S -n 1024 or something like: prctl -n process.max-file-descriptor -t basic -v 1024 -r -i process $$ These could go in amanda's .profile and that would help for login sessions, but I doubt it would help for cron started jobs. You may have to run it in a wrapper. With root access you can change the system default, but I doubt you want it changed at the system level. Maybe I'm wrong, you probably only need to change the amanda server(s). Jon -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (609) 477-8330 (C)
Re: amanda 3.3.3 too many files
Jean-Louis,
Yes, I did find some information on a run time mechanism to
increase the 256 file limit (file limit stored in unsigned character).
The work-around employes requires the exection of /usr/lib/extendedFILE.so.1
prior to the binary being executed.
Following up on your maxcheck and Spindle number, I wonder if I
couldn't automatically build an alternate disklist file with
spindle number and swap it in and out. It would have to be done
dynamically (since my disklist changes and making changes in
multiple locations is error prone), but that can be scripted and
called from cron.
/* I need something that will handle both formats of DLE
*
finsen /export2 zfs-snapshot2
finsen /export/home-AZ /export/home {
user-tar2
include ./[A-Z]*
}
*
*/
Since this is an amanda-client issue, rather than an amanda server
issue, I need to ask you, how to execute this on the client-side
before attempting to check the DLE list. Is there a way to invoke
this from the amanda daemon?
- Alternatively, if someone better versed than I am on the Solaris
inetd or in SMF knows how to insert the requisit command on the
client side - I would be appreciative if they would share their
information.
thank you,
Brian
On Wed, Jun 05, 2013 at 11:54:35AM -0400, Jean-Louis Martineau wrote:
Brian,
Can you increase the number of open files at the system level?
amcheck check all DLEs in parallel, you can try to add spindle (in the
disklist) to reduce parallelism but that can have a bad impact on dump
performance, so it is not a good workaround.
You would like a maxcheck setting similar to maxdump, I put it in my
TODO list.
Jean-Louis
On 06/05/2013 11:05 AM, Brian Cuttler wrote:
Hello amanda users,
I just updates amanda 3.3.0 to 3.3.0 on a Solaris 10/x86 system.
The system is both the server and the client, there are no other
clients of this system.
We have ~265 DLEs on this system (large zfs arrays and all
samba shares are their own file systems and DLE, thank goodness
I was able to talk my manager out of making all user directories
their own DLE as well, though they are their own zfs file systems).
The following errors are -not- new with 3.3.3, we've had them for
a while, I'd hoped the upgrade would take are of it.
Also the amcheck leaves an amanda-check file around for one of
the zfs file systems (yes, configured to use zfs snapshot). [I'm
pretty sure these two errors are related to one another]
The filesystem amanda-*-check file left is for the same filesystem
each night, unless we add/remove DLE/filesystems. So I think it is
the nth filesystem and at the limit of the open file counter, rather
than something in the file system itself.
I was hoping there was an easy fix for this. Last I recall on the
topic it had to do with the fillm being a 32 bit rather than 64 bit
value (I could be wrong about this).
Otherwise all # amcheck tests run successfully. Will run # amdump
this evening but do not anticipate any issues there.
thank you,
Brian
amcheck -c finsen
Amanda Backup Client Hosts Check
ERROR: finsen: service selfcheck: selfcheck: Error opening pipe to child:
Too many open files
ERROR: finsen: service /usr/local/libexec/amanda/selfcheck failed: pid
8590 exited with code 1
Client check: 1 host checked in 83.304 seconds. 2 problems found.
(brought to you by Amanda 3.3.3)
from /var/log/conlog
Jun 5 10:55:04 finsen amandad[8583]: [ID 927837 daemon.info] connect from
finsen.wadsworth.org
Jun 5 10:56:27 finsen selfcheck[8590]: [ID 702911 daemon.error] Error
opening pipe to child: Too many open files
---
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
---
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
Re: amanda 3.3.3 too many files
On 06/05/2013 01:41 PM, Brian Cuttler wrote:
Jean-Louis,
Yes, I did find some information on a run time mechanism to
increase the 256 file limit (file limit stored in unsigned character).
The work-around employes requires the exection of /usr/lib/extendedFILE.so.1
prior to the binary being executed.
Following up on your maxcheck and Spindle number, I wonder if I
couldn't automatically build an alternate disklist file with
spindle number and swap it in and out. It would have to be done
dynamically (since my disklist changes and making changes in
multiple locations is error prone), but that can be scripted and
called from cron.
/* I need something that will handle both formats of DLE
*
finsen /export2 zfs-snapshot2
finsen /export/home-AZ /export/home {
user-tar2
include ./[A-Z]*
}
*
*/
Since this is an amanda-client issue, rather than an amanda server
issue, I need to ask you, how to execute this on the client-side
before attempting to check the DLE list. Is there a way to invoke
this from the amanda daemon?
It must be done on the server before amcheck is executed.
./script-add-spindle disklist disklist.spindle
./amcheck CONF -odiskfile=disklist.spindle
Jean-Louis
Re: amanda 3.3.3 too many files
Jean-Louis,
Thank you, I'm sorry I was unclear. Yes, of course the disklist
needs to be in place when I invoke amcheck on the server.
I'd meant that I need to find out how to up the file limit on
the client, which is a more difficult proposition since its
SMF/INET and not simply something I can script in cron on the
server. The fact that the client and the server are the same
box doesn't help much in this case.
thank you,
Brian
On Wed, Jun 05, 2013 at 03:08:45PM -0400, Jean-Louis Martineau wrote:
On 06/05/2013 01:41 PM, Brian Cuttler wrote:
Jean-Louis,
Yes, I did find some information on a run time mechanism to
increase the 256 file limit (file limit stored in unsigned character).
The work-around employes requires the exection of
/usr/lib/extendedFILE.so.1
prior to the binary being executed.
Following up on your maxcheck and Spindle number, I wonder if I
couldn't automatically build an alternate disklist file with
spindle number and swap it in and out. It would have to be done
dynamically (since my disklist changes and making changes in
multiple locations is error prone), but that can be scripted and
called from cron.
/* I need something that will handle both formats of DLE
*
finsen /export2 zfs-snapshot2
finsen /export/home-AZ /export/home {
user-tar2
include ./[A-Z]*
}
*
*/
Since this is an amanda-client issue, rather than an amanda server
issue, I need to ask you, how to execute this on the client-side
before attempting to check the DLE list. Is there a way to invoke
this from the amanda daemon?
It must be done on the server before amcheck is executed.
./script-add-spindle disklist disklist.spindle
./amcheck CONF -odiskfile=disklist.spindle
Jean-Louis
---
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
Re: amanda 3.3.3 too many files
On 06/05/2013 03:56 PM, Brian Cuttler wrote:
Jean-Louis,
Thank you, I'm sorry I was unclear. Yes, of course the disklist
needs to be in place when I invoke amcheck on the server.
I'd meant that I need to find out how to up the file limit on
the client, which is a more difficult proposition since its
SMF/INET and not simply something I can script in cron on the
server. The fact that the client and the server are the same
box doesn't help much in this case.
It can help. use the 'local' auth, which is a fork of amandad instead of
connecting to it.
If you increase the limit for amcheck, then that amandad will get the
same limit.
Jean-Louis
thank you,
Brian
On Wed, Jun 05, 2013 at 03:08:45PM -0400, Jean-Louis Martineau wrote:
On 06/05/2013 01:41 PM, Brian Cuttler wrote:
Jean-Louis,
Yes, I did find some information on a run time mechanism to
increase the 256 file limit (file limit stored in unsigned character).
The work-around employes requires the exection of
/usr/lib/extendedFILE.so.1
prior to the binary being executed.
Following up on your maxcheck and Spindle number, I wonder if I
couldn't automatically build an alternate disklist file with
spindle number and swap it in and out. It would have to be done
dynamically (since my disklist changes and making changes in
multiple locations is error prone), but that can be scripted and
called from cron.
/* I need something that will handle both formats of DLE
*
finsen /export2 zfs-snapshot2
finsen /export/home-AZ /export/home {
user-tar2
include ./[A-Z]*
}
*
*/
Since this is an amanda-client issue, rather than an amanda server
issue, I need to ask you, how to execute this on the client-side
before attempting to check the DLE list. Is there a way to invoke
this from the amanda daemon?
It must be done on the server before amcheck is executed.
./script-add-spindle disklist disklist.spindle
./amcheck CONF -odiskfile=disklist.spindle
Jean-Louis
---
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
