Title: | VAX and Alpha VMS |
Notice: | This is a new VMSnotes, please read note 2.1 |
Moderator: | VAXAXP::BERNARDO |
Created: | Wed Jan 22 1997 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 703 |
Total number of notes: | 3722 |
Hello all, I have a customer running software raid V2.2 stripping on Openvms VAX V6.1. He reported to me that he has about 4 and 2 million blocks missing from his two bind set DPA500 and DPA600 respectively. I have advised him to do a $anal/disk DPA500: and calculate the allocated block instead of used block but it did not help. Any light sheded would be very much appreciated. Attach to the end of this note are the information collected from the customer. I have posted this same problem in COOKIE::RAID_SOFTWARE_FOR_OPENVMS conference because I am not sure which is the correct conference and customer need a reply by our tomorrow, sorry for any inconvenience caused. Best regards, -Eng- DEV NAME VOLUME TOTAL ALLOC FREE BR FREE RPT % DIFF ERR -------- ------ ----- ----- ------- -------- --- ---- --- DSA204 RTR_SYS1 8378028 4447872 3930156 3891303 46 38853 0 * DSA631 RTR_SYS2 8378028 2430297 5947731 5947677 70 54 0 DSA250 RTR_USERS 8378028 3899412 4478616 4478661 53 -45 0 DPA500 RTR_DB1 50188312 36932427 13255885 9096556 18 4159329 0 * DPA600 RTR_DBB1 16732792 7455095 9277697 6871315 41 2406382 0 * DPA610 RTR_DB2 16732792 346885 16385907 16385909 97 -2 0 DPA611 RTR_DBB2 16732792 178721 16554071 16554073 98 -2 0 DSA205 RTR_DB3 8378028 4673529 3704499 3704499 44 0 0 DSA630 RTR_DB4 8378028 432 8377596 8377596 99 0 0 ----------------------------------------------------------------------------- Total of 10 disk device(s) reported. A1RTR1-CSM> sh dev dpa Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt DPA0: (A1RTR1) Online 0 (remote access) DPA500: (A1RTR1) Mounted 0 RTR_DB1 9271094 102 2 DPA600: (A1RTR1) Mounted 0 RTR_DBB1 7007281 1 2 DPA610: (A1RTR1) Mounted 0 RTR_DB2 16385909 2 2 DPA611: (A1RTR1) Mounted 0 RTR_DBB2 16554073 1 2 A1RTR1-CSM> sh dev dpa500 /full Disk DPA500: (A1RTR1), device type RAID0 Disk Array, is online, mounted, file- oriented device, shareable, available to cluster, error logging is enabled. Error count 0 Operations completed 180054726 Owner process "" Owner UIC [SYSTEM] Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W Reference count 114 Default buffer size 512 Total blocks 50188312 Sectors per track 255 Total cylinders 772 Tracks per cylinder 255 Allocation class 256 Volume label "RTR_DB1" Relative volume number 0 Cluster size 49 Transaction count 117 Free blocks 9271094 Maximum files allowed 501883 Extend quantity 5 Mount count 2 Mount status System Cache name "_DSA100:XQPCACHE" Extent cache size 64 Maximum blocks in extent cache 927109 File ID cache size 64 Blocks currently in extent cache 896308 Quota cache size 0 Maximum buffers in FCP cache 2270 Volume owner UIC [1,1] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD Volume status: subject to mount verification, do not unload on dismount, write-back caching enabled. Volume is also mounted on A1RTR2. A1RTR1-CSM> dir dpa500:[000000...] /size/grand Grand total of 4 directories, 138 files, 36705298 blocks.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
655.1 | SET VOLUME/REBUILD=FORCE | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Wed May 28 1997 10:56 | 20 |
If you have a time-critical answer, you should raise an IPMT. On DPA500:, SHOW DEVICE reports 50,188,312 total blocks and free blocks of 9,271,094 -- meaning a current usage of around 40,917,218 blocks. This does not closely match the 36,705,298 block value returned by DIRECTORY/SIZE. (It's off by 4,211,920.) In addition to the ANALYZE/DISK, also run a pass of ANALYZE/DISK/REPAIR and SET VOLUME/REBUILD=FORCE on the target disk. The DIRECTORY/SIZE and (better) the DIRECTORY/SIZE=ALL commands can misreport the amount of actual usage. Particularly around hidden files and alias entries... SHOW DEVICE has had a history of being potentially incorrect, and this is often cleared by a disk rebuild or a reboot -- the value in memory does not necessarily reflect the actual usage. (There have been a few workarounds discussed over time, and there have been some changes made to better track the cases where there were accounting problems. See 126.* for one previous discussion...) | |||||
655.2 | UTRTSC::jgoras-197-2-3.jgo.dec.com::JurVanDerBurg | Change mode to Panic! | Thu May 29 1997 03:05 | 5 | |
Check for files which have been deleted but are still open. They won't show up in the directory but still take up space. Check with 'SHOW DEV/FILES' Jur. |