From: sirjofri <sirjofri+ml-9fans@sirjofri.de>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] 9Front / cwfs64x and hjfs storage
Date: Tue, 29 Dec 2020 08:53:55 +0000 (UTC) [thread overview]
Message-ID: <b60f836e-c27f-4463-b6bb-e5a2c1a25346@sirjofri.de> (raw)
In-Reply-To: <265706b3-155f-45d7-bfb3-da24d745bc79@www.fastmail.com>
Hello,
29.12.2020 03:27:19 Ethan Gardener <eekee57@fastmail.fm>:
> You can add disks. CWFS config allows multiple devices/partitions to
form the WORM. It's like a simple form of LVM. I forget the exact syntax
and I don't think there's a man page documenting cwfs's particular
variant syntax, but I think it's something like (/dev/sdE0/worm
/dev/sdF0/worm) in place of just /dev/sdE0/worm
Is it then also possible to remove older disks at some point
(physically)? Something like this:
- WORM1 (full)
- WORM2 (full)
- WORM3 (not full)
- cache
Then removing WORM1, storing it as backup or reformat it as a new WORM4:
- WORM2 (full)
- WORM3 (not full)
- WORM4 (new, empty)
- cache
Is something like that possible? If not, it still could be an inspiration
for ori's new filesystem, maybe?
sirjofri
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc951a224dde6dde5-Md728027c4f6ed59af86e6aaf
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2020-12-29 8:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 23:55 joey
2020-12-29 2:27 ` Ethan Gardener
2020-12-29 8:53 ` sirjofri [this message]
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=b60f836e-c27f-4463-b6bb-e5a2c1a25346@sirjofri.de \
--to=sirjofri+ml-9fans@sirjofri.de \
--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).