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
Hi Friends,
Does any impact on quota re-initialize? we are seeng error message as "quota.parse.error: skipping new definition for /vol/vol1/qtreex ". Please suggest best solution.
Solved! See The Solution
1 ACCEPTED SOLUTION
Storage6 has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The only risk I’m aware of is that the report you see now in the GUI is not up-to-date, and once you re-initialise the quota rules you have across the volume will start applying again after (I assume) some time that they haven’t .
Hence don’t trust the figures you see there - if you suspect some hard quota been breached while it was off - increase it before re-initialising it or you might have write failures.
Gidi Marcus (Linkedin) - Storage and Microsoft technologies consultant - Hydro IT LTD - UK
1 REPLY 1
Storage6 has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The only risk I’m aware of is that the report you see now in the GUI is not up-to-date, and once you re-initialise the quota rules you have across the volume will start applying again after (I assume) some time that they haven’t .
Hence don’t trust the figures you see there - if you suspect some hard quota been breached while it was off - increase it before re-initialising it or you might have write failures.
Gidi Marcus (Linkedin) - Storage and Microsoft technologies consultant - Hydro IT LTD - UK
