HSM Problem
Hi Guys and Girls, I experience some weird HSM Problem under AIX using client version 4.1.2.20: I let dsmautomig run manually once at night via crontab. I have stderr redirected to a log file and last night I got a whole lot of this error: 11/19/02 15:33:25 OpenDB:PrepareAccess-2 Cannot open database /sambaarch/.SpaceMan/premigrdb: The process file table is full. Can anyone explain to me what this means and how to rectify it?? THNX Lars
Re: HSM problem
Richard, Yes, I just install HSM two weeks ago. But I have restarted the Solaris machine several times and the kernel extension has been added. Indeed, the rest of the file systems have been created with the same process at the same time, and they work okey. When I do "df" the output is: # df / (/dev/dsk/c0t0d0s0 ): 1038738 blocks 357605 files /proc (/proc ): 0 blocks 1896 files /dev/fd(fd): 0 blocks0 files /swaptmp (swap ): 1066576 blocks19536 files /discoext/pool04 (/dev/vx/dsk/rootdg/vol03):6562 blocks 818 files /discoext/pool06 (/dev/vx/dsk/rootdg/vol04): 18060 blocks 2255 files /discoext/pool01 (/dev/vx/dsk/rootdg/vol02):6560 blocks 817 files /discoext/pool03 (/dev/vx/dsk/rootdg/vol06):1056 blocks 129 files /discoext/pool07 (/dev/vx/dsk/rootdg/vol01):5578 blocks 695 files /home/uitpzdn (ztv102:/export/home/gu17/uitpzdn): 252528 blocks 223478 files /itpzad/gen(ztv101:/itpzad/gen/sun4u_SunOS_5.6): 2296688 blocks 287085 files /discoext/pool02 (/dev/vx/dsk/rootdg/vol05):9122 blocks 3826 files /discoext/pool08 (/dev/vx/dsk/rootdg/vol07): 2094436 blocks 261803 files None of them are mounted twice. I understand that AIX and Solaris does not work the same with this. Thank you very much, Eva - > Eva - Did you just install HSM? I suspect so, if you are just now > experimenting with creating an HSM-managed file system. > If that is the case, then you probably have not restarted Solaris, > which would then have executed /etc/rc.adsmhsm (in /etc/inittab, at > least it is in AIX) to add the kernel extensions to support the > FSM. From http://people.bu.edu/rbs/ADSM.QuickFacts : > > File System Migrator (FSM)A kernel extension that is mounted > over > an operating system file system when > space management is added to the > file > system (over JFS). The file system > migrator intercepts all file system > operations and provides any space > management support that is required. > If > no space management support is > required, > the operation is performed by the > operating system file system. > > If you do simply: 'df', and do not see your HSM file system mounted twice, > then it's not HSM controlled. (The first mount is the opsys file system; > the second is FSM taking over the opsys file system.) > >Richard
Re: HSM Problem
I just checked my error log file, and seems back in April we had a bunch of these errors too (which was before I took over the tsm admin duties). Thought at first it might be that the Quota was too low (dsmmigfs query ). But mine appears to be ok. I don't have a need to migrate files very often, which is probably why it hasn't occurred since then. Let me know if you find anything out. --- Lars Bebensee <[EMAIL PROTECTED]> wrote: > Hi Guys and Girls, > > I experience some weird HSM Problem under AIX using > client version > 4.1.2.20: > I let dsmautomig run manually once at night via > crontab. I have stderr > redirected to a log file and last night I got a > whole lot of this error: > > 11/19/02 15:33:25 OpenDB:PrepareAccess-2 Cannot > open database > /sambaarch/.SpaceMan/premigrdb: The process file > table is full. > > Can anyone explain to me what this means and how to > rectify it?? > > THNX > > Lars __ Do you Yahoo!? Yahoo! Web Hosting - Let the expert host your site http://webhosting.yahoo.com
TSM/HSM problem writing to filesystem
We are experiencing a problem writing data to our HSM-managed filesystem. The HSM-managed filesystem is on the same system as the server, which is running AIX 4.3.3, TSM Server 4.1.3, TSM Client 4.1.2. Although there is plenty of available disk space in the HSM-managed filesystem and it is nowhere near its migration threshold, we are experiencing errors when trying to create files in the filesystem. For example, hostname>cp SOL-002 sol cp: sol: There is not enough memory available now. hostname> ./testlooper dd: write error: Not enough space Attempts to retrieve files off of the HSM tapes also result in an error: ANS9283K Tivoli Space Manager is recalling a migrated file. ANS9285K Cannot complete remote file access. I looked up ANS9285K in the Messages Manual - it says to check if the server has been disabled. The server is up and running and has been running backups successfully, including those on the HSM-managed filesystem. There is 500 Megabytes of free memory on the server just now. Errors don't occur for every file in the filesystem. The errors just started happening yesterday. There are no errors in errpt, console log, or dsm logs. Our db and log are not full, there are available tapes. Any ideas what the problem/solution might be? -- Mary Stephenson [EMAIL PROTECTED] Academic Computing & Network Services Florida State University
Re: TSM/HSM problem writing to filesystem
> ANS9285K Cannot complete remote file access. > > I looked up ANS9285K in the Messages Manual - it says to check > if the server has been disabled. The server is up and running > and has been running backups successfully, including those on > the HSM-managed filesystem. Mary - Your backup server is not necessarily your HSM server. Given your recent migration, you may have, or need, a MIgrateserver option in your client options file to point to the proper HSM server. Richard Sims, BU
Re: TSM/HSM problem writing to filesystem
Hi It shows that Memory not available not no space in filesystem.Pl look at vmstat 4 th coloumn after avm column it should show some me at least 128 .If its low then run crush command say crush 1. 1 stands for pages. Then memory will be released.Then try to copy.I feel ur ram is too low.Some process do not continue due to low free space. BALANAND PINNI. PHONE 314-206-5911. EM:[EMAIL PROTECTED] PG:1-800-451-6897. -Original Message- From: Mary Stephenson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 24, 2001 9:09 AM To: [EMAIL PROTECTED] Subject: TSM/HSM problem writing to filesystem We are experiencing a problem writing data to our HSM-managed filesystem. The HSM-managed filesystem is on the same system as the server, which is running AIX 4.3.3, TSM Server 4.1.3, TSM Client 4.1.2. Although there is plenty of available disk space in the HSM-managed filesystem and it is nowhere near its migration threshold, we are experiencing errors when trying to create files in the filesystem. For example, hostname>cp SOL-002 sol cp: sol: There is not enough memory available now. hostname> ./testlooper dd: write error: Not enough space Attempts to retrieve files off of the HSM tapes also result in an error: ANS9283K Tivoli Space Manager is recalling a migrated file. ANS9285K Cannot complete remote file access. I looked up ANS9285K in the Messages Manual - it says to check if the server has been disabled. The server is up and running and has been running backups successfully, including those on the HSM-managed filesystem. There is 500 Megabytes of free memory on the server just now. Errors don't occur for every file in the filesystem. The errors just started happening yesterday. There are no errors in errpt, console log, or dsm logs. Our db and log are not full, there are available tapes. Any ideas what the problem/solution might be? -- Mary Stephenson [EMAIL PROTECTED] Academic Computing & Network Services Florida State University PINNI, BALANAND (SBCSI).vcf
Re: TSM/HSM problem writing to filesystem
it looks like an OS problem maybe no more available inodes or file table entries ? of course if you can't even copy a file it's not a tsm problem... A 10:09 24/04/01 -0400, vous avez écrit : > We are experiencing a problem writing data to our > HSM-managed filesystem. > > The HSM-managed filesystem is on the same system as > the server, which is running AIX 4.3.3, TSM Server 4.1.3, > TSM Client 4.1.2. > > Although there is plenty of available disk space in the > HSM-managed filesystem and it is nowhere near its > migration threshold, we are experiencing errors when > trying to create files in the filesystem. > > For example, > > hostname>cp SOL-002 sol > cp: sol: There is not enough memory available now. > > hostname> ./testlooper > dd: write error: Not enough space > > Attempts to retrieve files off of the HSM tapes also > result in an error: > > ANS9283K Tivoli Space Manager is recalling a migrated file. > ANS9285K Cannot complete remote file access. > > > I looked up ANS9285K in the Messages Manual - it says to check > if the server has been disabled. The server is up and running > and has been running backups successfully, including those on > the HSM-managed filesystem. There is 500 Megabytes of free > memory on the server just now. > > Errors don't occur for every file in the filesystem. > The errors just started happening yesterday. > > There are no errors in errpt, console log, or dsm logs. > > Our db and log are not full, there are available tapes. > > Any ideas what the problem/solution might be? > > >-- > Mary Stephenson > [EMAIL PROTECTED] > Academic Computing & Network Services > Florida State University > > - * - * - * - * - * - * - Mes idees n'engagent que moi (vieux proverbe du Net) Thierry ITTY eMail : [EMAIL PROTECTED] FRANCE
Re: TSM/HSM problem writing to filesystem
I would also look into that direction. And: Is your filesystem "large file enabled"? I vaguely remember having read about possible problems, when a large file enabled filesystem is crowded with small files (and the stubs are small). Something in the sense, that free space actually exists but cannot be used. Might be worth to have a look at defragmentation? > it looks like an OS problem > maybe no more available inodes or file table entries ? > of course if you can't even copy a file it's not a tsm problem... > > > > A 10:09 24/04/01 -0400, vous avez écrit : > > We are experiencing a problem writing data to our > > HSM-managed filesystem. > > > > The HSM-managed filesystem is on the same system as > > the server, which is running AIX 4.3.3, TSM Server 4.1.3, > > TSM Client 4.1.2. > > > > Although there is plenty of available disk space in the > > HSM-managed filesystem and it is nowhere near its > > migration threshold, we are experiencing errors when > > trying to create files in the filesystem. > > > > For example, > > > > hostname>cp SOL-002 sol > > cp: sol: There is not enough memory available now. > > > > hostname> ./testlooper > > dd: write error: Not enough space > > > > Attempts to retrieve files off of the HSM tapes also > > result in an error: > > > > ANS9283K Tivoli Space Manager is recalling a migrated file. > > ANS9285K Cannot complete remote file access. > > > > > > I looked up ANS9285K in the Messages Manual - it says to check > > if the server has been disabled. The server is up and running > > and has been running backups successfully, including those on > > the HSM-managed filesystem. There is 500 Megabytes of free > > memory on the server just now. > > > > Errors don't occur for every file in the filesystem. > > The errors just started happening yesterday. > > > > There are no errors in errpt, console log, or dsm logs. > > > > Our db and log are not full, there are available tapes. > > > > Any ideas what the problem/solution might be? > > > > > >-- > > Mary Stephenson > > [EMAIL PROTECTED] > > Academic Computing & Network Services > > Florida State University > > > > > - * - * - * - * - * - * - > Mes idees n'engagent que moi (vieux proverbe du Net) > > Thierry ITTY > eMail : [EMAIL PROTECTED] FRANCE -- Reinhard MerschWestfaelische Wilhelms-Universitaet Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum Roentgenstrasse 9-13, D-48149 Muenster, Germany Tel: +49(251)83-31583 E-Mail: [EMAIL PROTECTED] Fax: +49(251)83-31653
