From: joey@plan9.white-swift.com
To: 9fans <9fans@9fans.net>
Subject: [9fans] 9Front / cwfs64x and hjfs storage
Date: Mon, 28 Dec 2020 18:55:52 -0500 [thread overview]
Message-ID: <16091997520.72404.916174@composer.9fans.topicbox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
Hello,
While it is not yet a concern, I am trying to figure something out that does not seem to be well documented in the man pages or the fqa about the file systems.
I am currently running a plan9front instance with cwfs64x (the whole "hjfs is experimental, you could loose your files" seemed to be a bit dangerous when I started everything) and I understand that it is a WORM file system. My question is for the end game. If the storage gets full with all of the diffs, is there a way for the oldest ones to roll off, or do you need to expand the storage or export them or ? I come from the linux world where this is not a feature file system wise and worst case I would have lvm's that I could just grow or with repos I could cull the older diffs, if needed.
If there is additional features for this in hjfs, that would be nice to know too. I am just really trying to understand the limits of the technology and what expectations to have. Otherwise, I love the plan9 environment and knowing what options I have for when I inevitably get to that point would put me more at ease in trusting more operations to be conducted on Plan9 systems.
Best and thank you!
~Joey
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc951a224dde6dde5-M58a27bc5d68fd6f7b293a922
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2076 bytes --]
next reply other threads:[~2020-12-28 23:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 23:55 joey [this message]
2020-12-29 2:27 ` Ethan Gardener
2020-12-29 8:53 ` sirjofri
2020-12-29 9:15 ` Kurt H Maier
2020-12-29 9:21 ` sirjofri
2021-01-07 21:28 ` Stuart Morrow
2021-01-07 23:25 ` ori
2021-02-08 1:35 ` Ryan
2021-02-08 6:14 ` Ethan Gardener
2020-12-29 13:06 ` Alex Musolino
2020-12-29 16:14 ` Ethan Gardener
2020-12-30 8:08 ` joey
2021-02-04 23:10 ` rt9f.3141
2021-02-05 2:51 ` rt9f.3141
2021-02-05 3:06 ` Alex Musolino
2021-02-07 6:37 ` rt9f.3141
2021-02-07 22:54 ` rt9f.3141
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16091997520.72404.916174@composer.9fans.topicbox.com \
--to=joey@plan9.white-swift.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).