NAS bucket and FlexCache write-back mode
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Locate the source file for the ONTAP FlexCache 'Supported and unsupported features' topic (page URL: docs.netapp.com/us-en/ontap/flexcache/supported-unsupported-features-concept.html) in this repo, and compare it with the flexcache-duality-faq topic that already contains the statement. Add an equivalent note stating NAS buckets on FlexCache volumes do not support FlexCache write-back, keeping the existing markup style of that page, then confirm the rendered output matches the wording shown in the issue screenshots.
Written by the indexing model from the issue text.
Description
Page URL
https://docs.netapp.com/us-en/ontap/flexcache/supported-unsupported-features-concept.html
Page title
Supported and unsupported features for ONTAP FlexCache volumes
Summary
Could you please add a note stating that NAS buckets on FlexCache volumes do not support FlexCache write-back?
This is mentioned in the FAQ below, but
https://docs.netapp.com/us-en/ontap/flexcache/flexcache-duality-faq.html
please also include it on this page.
https://docs.netapp.com/us-en/ontap/flexcache/supported-unsupported-features-concept.html
Public issues must not contain sensitive information
- This issue contains no sensitive information.
- Dominant language
- No language data
- Stars
- 39
- Forks
- 87
- Avg merge
- 2h 1m
- Merged PRs (30d)
- 11
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NetAppDocs/ontap
-
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
NetAppDocs/ontap#2157 ·
Maintainers usually reply within 1 day
-
ONTAP S3 versioningOpen
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
NetAppDocs/ontap#2152 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
NetAppDocs/ontap#2151 · 2 comments ·
Maintainers usually reply within 1 day
-
"For SVM disaster recovery for SVM migration" table should start with most recent ONTAP versionsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
NetAppDocs/ontap#2149 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
NetAppDocs/ontap#2145 ·
Maintainers usually reply within 1 day
All issues in NetAppDocs/ontap
Similar issues
-
docs good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Usenova-Labs/usenova-backend#36 ·
Maintainers usually reply within 1 day
-
git: README should state plainly that without --repository every reachable repository is in scopeOpendocumentation server-git v2
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
modelcontextprotocol/servers#5225 ·
Maintainers usually reply within 1 day
-
Changelog lists three bar periods for bars of a day or longer but custom timeframes use anotherOpendata documentation
Difficulty 1/5 Under an hour Newbie friendliness 95/100
userFRM/egui-charts#623 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/vscode-docs#10534 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
Droid-Deck/DroidDeck#1355 ·
Maintainers usually reply within 1 day