From: slash <slash.9fans@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] New disk, i/o error
Date: Mon, 17 Oct 2011 07:17:55 -0400 [thread overview]
Message-ID: <CAEaiYYybGsnF8smOMFwXTPUBh4Wm4RtcqOP8iYrLjr4_3tC5-A@mail.gmail.com> (raw)
In-Reply-To: <b8c5797c94d45b58033847b47953676e@quintile.net>
> How did you used disk/prep?
I ran 'disk/prep -bw -a^(9fat nvram fossil swap) /dev/sdE1/plan9'.
When I ran it, my old disk was sdE0 and the new was sdE1. Now I notice
the layout prep created is identical on both disks!
su# disk/prep /dev/sdE0/plan9 # old
9fat 0 204800 (204800 sectors, 100.00 MB)
nvram 204800 204801 (1 sectors, 512 B )
fossil 204801 389668226 (389463425 sectors, 185.71 GB)
swap 389668226 390716802 (1048576 sectors, 512.00 MB)
>>> q
su# disk/prep /dev/sdE1/plan9 # new
9fat 0 204800 (204800 sectors, 100.00 MB)
nvram 204800 204801 (1 sectors, 512 B )
fossil 204801 389668226 (389463425 sectors, 185.71 GB)
swap 389668226 390716802 (1048576 sectors, 512.00 MB)
empty 390716802 3907024002 (3516307200 sectors, 1.63 TB)
>>> q
> I don't believe you can, fossil is usually used with venti and venti can definitely
> be grown on the fly, fossil alone is normally confined to just laptops where this is
> not an issue.
Will this work:
1. boot off the old disk (/dev/sdE0/plan9)
2. disk/prep /dev/sdE1/plan9
- delete swap and fossil
- create a new fossil at the same offset as the old one but bigger
- write changes
3. mount /dev/sdE1/fossil
I am trying to find a way to resize /dev/sdE1/fossil without losing
the existing data on it.
next prev parent reply other threads:[~2011-10-17 11:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEaiYYwtJPmt-utC12NwucXQhJ6kKs0CzBXZRT6PU=fCZnjpbA@mail.gmail.c>
2011-10-16 15:20 ` erik quanstrom
2011-10-16 15:51 ` slash
[not found] ` <CAEaiYYxsDmZ_O8N0BwK5Ch071NGbgrb_MyAnupxCyWgRioSTrw@mail.gmail.c>
2011-10-16 17:29 ` erik quanstrom
2011-10-16 19:19 ` slash
2011-10-16 20:13 ` slash
[not found] ` <CAEaiYYwfHD0d+SyTLqVVi-si=knjSqH6FKP61pkR-XRo5ixegA@mail.gmail.c>
2011-10-16 20:40 ` erik quanstrom
2011-10-17 1:54 ` slash
2011-10-17 7:44 ` David du Colombier
2011-10-17 10:23 ` Steve Simon
2011-10-17 11:17 ` slash [this message]
2011-10-17 12:15 ` David du Colombier
2011-10-17 11:56 ` David du Colombier
2011-10-17 15:43 ` Lyndon Nerenberg
2011-10-17 16:15 ` erik quanstrom
2011-10-17 16:46 ` Lyndon Nerenberg
[not found] ` <CAEaiYYys==oFZ7Umr4SD+rT6wtRo=j4K6wd0950gU94cGiR6kw@mail.gmail.c>
2011-10-17 3:28 ` erik quanstrom
2011-10-16 20:43 ` Steve Simon
2011-10-19 11:48 ` Peter A. Cejchan
2011-10-16 14:11 slash
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=CAEaiYYybGsnF8smOMFwXTPUBh4Wm4RtcqOP8iYrLjr4_3tC5-A@mail.gmail.com \
--to=slash.9fans@gmail.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).