Just got our big-honkin RedHat AS4 TSM server (5.4.0.0) up and running and started to use it and are now experiencing errors in the volumes of the LZ.
The LZ is in a 4.7TB filesystem. So far, the errors have been occuring against volumes in the >3TB area (we divided the volumes into 250GB pieces, making sure to format them 1-at a time, to not cause fragmentation). 5/31/2007 10:29:08 AM ANR8555E An error (5, ) occurred during a read operation from disk /tsmpool/stg13.dsm. 5/31/2007 10:29:08 AM ANR9999D dsrtrv.c(1030): ThreadId Error on volume /tsmpool/stg13.dsm: execRc=-1, summaryRc=-1. 5/31/2007 10:29:08 AM ANR9999D dsrtrv.c(1041): ThreadId --> Volume /tsmpool/stg13.dsm, Starting Logical Block 1186847, Blocks in Range 64. We didn't have any problems during the formatting. Seeing similar errors in the /var/log/messages file: May 31 10:29:08 fireball kernel: attempt to access beyond end of device May 31 10:29:08 fireball kernel: sdb1: rw=0, want=34359738368, limit=10248519613 May 31 10:29:08 fireball kernel: attempt to access beyond end of device May 31 10:29:08 fireball kernel: sdb1: rw=0, want=34359738368, limit=10248519613 May 31 10:29:08 fireball kernel: attempt to access beyond end of device May 31 10:29:08 fireball kernel: sdb1: rw=0, want=34359738368, limit=10248519613 Anybody deal with something like this ? Anybody have a linux server with >2TB filesystems ? ---------------------------------------------------- Zoltan Forray Virginia Commonwealth University Office of Technology Services University Computing Center e-mail: [EMAIL PROTECTED] voice: 804-828-4807
