From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] add new disk drives to fs.
Date: Mon, 23 Apr 2001 13:03:48 +0100 [thread overview]
Message-ID: <20010423120319.4BE0B19AEA@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1840 bytes --]
i normally do something like this, which might be less work, and doesn't
require an intermediate copy of the file system (unless you'd like
the backup, which you might). i was going to send this privately but
i'll post it to the list in case i've slipped up somewhere.
add the new discs to the file server, leaving the original one as well,
being sure to use distinct SCSI IDs.
create a new file system on the new devices, initialise it and set allow mode
filsys newfs [w2w3] # or whatever your configuration is for the new devices
ream newfs # be very careful to ream the right name!
allow
now you've got access to both the original main and empty newfs
file systems at the same time from the cpu server or terminals.
copy from one to another, preserving permissions and ownership
# mount existing file system on /n/boot so as to avoid copying files in /net and /dev(!)
9fs boot
# mount the destination file system on /n/tapefs (or some other name)
mount -c /srv/boot /n/tapefs newfs # note the `newfs' argument to select other than `main'
you can do some test file creations, writes and removals on /n/tapefs.
# copy the files, preserving permissions
disk/mkfs -a -s /n/boot /lib/proto/allproto | disk/mkext -u -d /n/tapefs
in this last command, again be sure that /n/boot looks right and /n/tapefs was correctly
mounted from the file server, and that you've typed it in correctly
(and that what i gave you makes sense),
because you're in allow mode without a safety net.
then `halt' the file server, remove the old disc and enter config mode.
i'll use the same scsi IDs as above but with the old device out you could
renumber with appropriate changes.
config w2 # or whatever is appropriate
# re-enter your ip ipmask ipgw and service name
filsys main [w2w3]
end
[-- Attachment #2: Type: message/rfc822, Size: 2214 bytes --]
To: cse.psu.edu!9fans
Subject: [9fans] add new disk drives to fs.
Date: Mon, 23 Apr 2001 17:12:45 +0900
Message-ID: <27798.988013565@beat.cc.titech.ac.jp>
I live on a file server with a 2GB SCSI disk reamed by
`filsys main w0'. Having got new disk drives, I want to
add these to the `main'.
my imagined steps:
1: boot a cpu/auth server from a local disk.
2: mount the fs on /n/myfs.
3: `wrap/create' the above /n/myfs to some remote ftpfs filesystem.
4: `filsys' and `ream' the fs with new disks
5: `wrap/inst' the `wrap/create'd the /n/myfs to the fs's /
Do you think the above steps will do?
I want advise about permission and date issue
that may concern in the step 3 especially.
Thank you.
--
YAMANASHI Takeshi.
next reply other threads:[~2001-04-23 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 12:03 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-23 8:12 YAMANASHI Takeshi
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=20010423120319.4BE0B19AEA@mail.cse.psu.edu \
--to=forsyth@vitanuova.com \
--cc=9fans@cse.psu.edu \
/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).