Steven,
What is the filesystem type for the usb drive?
Do you have any messages in the os logs?
Could the filesystem be running out of inodes?
len
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Steven Haigh
Sent: Thursday, March 04, 2010 6:27 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] ANR8341I End-of-volume reached for REMOVABLEFILE volume
On 07/02/2010, at 12:45 PM, Steven Haigh wrote:
> On Sun, 07 Feb 2010 09:25:01 +1100, Steven Haigh <netwiz AT crc.id DOT au>
> wrote:
>> On Sat, 6 Feb 2010 13:33:57 -0500, Richard Sims <rbs AT BU DOT EDU> wrote:
>>> (file system), and that your Unix resource limit "filesize" is not
>>> restricting the size. Also beware file size limits for a chosen file
>>> system type, which can be influenced by the block size chosen when the
>>> file system was initialized.
>
> I should also mention that the following is set for ulimit:
>
> # ulimit -a
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> scheduling priority (-e) 0
> file size (blocks, -f) unlimited
> pending signals (-i) 24575
> max locked memory (kbytes, -l) 32
> max memory size (kbytes, -m) unlimited
> open files (-n) 1024
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 10240
> cpu time (seconds, -t) unlimited
> max user processes (-u) unlimited
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
>
> These are all defaults. As such I didn't think about checking them before
> until I re-read your message.
Ok. I've got a bit of time at the moment so I thought I'd revisit this.
I'm in the middle of shifting data back from the USB drives to the main storage
array and making that much bigger to accommodate the data. This test system
only used a 40Gb pool on the main raid array - everything else gets shipped out
to the USB drives via a migration.
To recap the issue, I've noticed is that when a drive is around 50-60% full I
get an ANR8341I End-of-volume event in the logs and a new volume is asked for.
While I would expect this for a full volume, I wouldn't expect it with a half
full volume.
I have copied the most relevant information
below:
tsm: SERVER1>q devclass usbdrive f=d
Device Class Name: USBDRIVE
Device Access Strategy: Sequential
Storage Pool Count: 1
Device Type: REMOVABLEFILE
Format: DRIVE
Est/Max Capacity (MB): 100,000.0
Mount Limit: DRIVES
Mount Wait (min): 5,760
Mount Retention (min): 0
Label Prefix:
Library: USBDRIVES
Directory:
Server Name:
Retry Period:
Retry Interval:
Shared:
High-level Address:
Minimum Capacity:
WORM: No
Drive Encryption:
Scaled Capacity:
Last Update by (administrator): ADMIN
Last Update Date/Time: 01/21/2010 15:57:58
When the volume gets full, I get the following:
01/24/2010 14:46:49 ANR8335I 003: Verifying label of REMOVABLEFILE
volume 5QD7CKPM in drive USBDRIVE (/mnt/usb). (PROCESS: 5)
01/24/2010 14:46:49 ANR8328I 003: REMOVABLEFILE volume 5QD7CKPM
mounted in drive USBDRIVE (/mnt/usb). (PROCESS: 5)
01/24/2010 14:46:49 ANR8340I REMOVABLEFILE volume 5QD7CKPM mounted.
(PROCESS: 5)
01/24/2010 14:46:49 ANR0513I Process 5 opened output volume 5QD7CKPM.
(PROCESS: 5)
01/24/2010 14:46:49 ANR8341I End-of-volume reached for REMOVABLEFILE
volume 5QD7CKPM. (PROCESS: 5)
01/24/2010 14:46:49 ANR0515I Process 5 closed volume 5QD7CKPM.
(PROCESS: 5)
01/24/2010 14:46:49 ANR8468I REMOVABLEFILE volume 5QD7CKPM dismounted
from drive USBDRIVE (/mnt/usb) in library USBDRIVES. (PROCESS: 5)
01/24/2010 14:46:49 ANR8326I 004: Mount REMOVABLEFILE volume SCRTCH
R/W in drive USBDRIVE (/mnt/usb) of library USBDRIVES within 5760 minutes.
(PROCESS: 5)
When looking at the filesystem, I see:
Filesystem Size Used Avail Use% Mounted on
/dev/sdk1 294G 180G 99G 65% /mnt/usb
# ls -l
total 188260336
-rw------- 1 root root 192590295715 Jan 21 18:26 5QD7CKPM
drwx------ 2 root root 16384 Jan 7 12:54 lost+found
--
Steven Haigh
Email: netwiz AT crc.id DOT au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
|
