From: beto@plan9.cs.su.oz.au beto@plan9.cs.su.oz.au
Subject: My pseudo worm is getting crouded ...
Date: Wed, 3 Apr 1996 09:44:22 -0500 [thread overview]
Message-ID: <19960403144422.nlPROUeubRtMZU_kbbJz3dpKsLwywM0jzcwL24-2GBA@z> (raw)
In <9603251139.AA10775@nsof.co.il>
blumzi@nsof.co.il (Arie Blumenzweig) wrote:
> Hi,
>
> Can this be done? Did anyone do it and survive?
>
I did something similar but not exactly the same.
I was using a MIPS machine as a file server with a
4G SCSI disk as the main file system. I wasn't using
a fake worm partition becuase the data there was
also inmutable. Eventually I ran out of space, so I was
able to attach another SCSI disk then redefine main as
the concatenation of the old and a new 4G disk.
The procedure was:
0) recompile the kernel with the new file system
size. the kernel does not calcualte the size
of the file system based on main definition, it
read it from the super block.
1) config mode
- filsys main (wOLDwNEW)
2) normal mode
- then run check free which will recreate the
free list and hopefully add the new blocks to the
free list.
However, what you want do it's a bit different:
- You won't have to run check free becuase
bufalloc will add more block to the free
list of demand, which is good.
- If had a look to the fworm implementation and
it uses a part of the device to detect if a block
is written twice or read without been written first.
So you would probably have to ream both disk
again, which would destroy your data :-(.
It looks to me that the easiest thing is to backup
your files restart a new file system with the
two disks, restore the backup and wait until
5 pm, however you'll loose the history. Another
posibility is to add a command to the kernel to
combine both disks into a new fworm, but please
backup your disk first.
next reply other threads:[~1996-04-03 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-03 14:44 beto [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-03-25 11:39 Arie
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=19960403144422.nlPROUeubRtMZU_kbbJz3dpKsLwywM0jzcwL24-2GBA@z \
--to=beto@plan9.cs.su.oz.au \
/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).