Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We have OSSV jobs failing reporting no space available on the destination volume. Can someone help me understand the output of this df-h command, I can't understand how it calculates we're using 99% of the available space.
VOLUME total used avail capacity
/volume 3612GB 1350GB 41GB 99
/volume/.snapshot 73GB 290GB 0GB 394
1) For /volume If 1350GB are used on a 3612GB volume, surely the available space is 2,262GB
2) For .snapshot. How can 394% of the total be used?
The snapshot reserve is set to 2%. There aren't any quotas. There are no space guarentees.
Solved! See The Solution
1 ACCEPTED SOLUTION
Drew_C has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1) For /volume If 1350GB are used on a 3612GB volume, surely the available space is 2,262GB
As you said, no space-guarantees, that means 'aggregate space' availability is key here. Could you check the space usage of the aggregate of the affected volume? You might be running low on space on the aggregate. Let us know.
2) For .snapshot. How can 394% of the total be used?
Yes, it can happen with NetApp ONTAP volumes. Total volume space = Active File-system space + Space reserve. In your case, it is set to '2%' of 3612g = approx. 73G, which means Active Filesystem cannot write into this space (72g), it is strictly for 'snapshots'. However, snapshots can spill-over to AFS. In other words, snapshots filled-up the reserved space and then started to spill-over to the Active File-system. The percentage of 394 suggests, it used 394 % of the total reserved space, ie. 394 * 73 / 100 = approx. 290g. You may want to look at your snapshots frequency/schedule or setup some auto-delete mechanism etc.
1 REPLY 1
Drew_C has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1) For /volume If 1350GB are used on a 3612GB volume, surely the available space is 2,262GB
As you said, no space-guarantees, that means 'aggregate space' availability is key here. Could you check the space usage of the aggregate of the affected volume? You might be running low on space on the aggregate. Let us know.
2) For .snapshot. How can 394% of the total be used?
Yes, it can happen with NetApp ONTAP volumes. Total volume space = Active File-system space + Space reserve. In your case, it is set to '2%' of 3612g = approx. 73G, which means Active Filesystem cannot write into this space (72g), it is strictly for 'snapshots'. However, snapshots can spill-over to AFS. In other words, snapshots filled-up the reserved space and then started to spill-over to the Active File-system. The percentage of 394 suggests, it used 394 % of the total reserved space, ie. 394 * 73 / 100 = approx. 290g. You may want to look at your snapshots frequency/schedule or setup some auto-delete mechanism etc.
