I have 2 yrs old 1TB SATA Caviar that most of its lifetime spent in a bin in
my table... waiting just for data backup (ext2)... after 2yrs2months (and
only few hours really spinning) it has 16 bad sectors, sigh ... it is
WD1002FBYS ... just warning, regards,
++pac
do you find you need swap to run plan 9 on these
systems?
Nope -- a testament to the system. But that doesn't negate the fact that
'throw more hardware at it' isn't always an option.
On Mon Oct 17 11:45:26 EDT 2011, lyn...@orthanc.ca wrote:
> > this is not such a pain as it might appear, swapping makes performance
> > so miserable its not really worth having, especially given how cheap a
> > few GB of RAM is these days.
>
> Not always an option on, say, PC-104 systems.
do you
this is not such a pain as it might appear, swapping makes performance
so miserable its not really worth having, especially given how cheap a
few GB of RAM is these days.
Not always an option on, say, PC-104 systems.
> 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/sd
> > Why did prep create a 512MB swap
> > partition when I have 2GB RAM?
>
> good question, though on a positive note swap doesn't work anyway
> (except on the 9front form) so I would delete it as if the machine
> starts to swak it could wedge.
>
> this is not such a pain as it might appear, swapp
> 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
9fat0 204800 (
> Can I grow fossil on the fly?
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.
> Why did prep create a 512MB swap
> partition when I have 2GB RAM?
good questi
> Indeed!
>
> su# disk/prep /dev/sdE0/plan9
> 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
> Can I grow fossil on the fly? Why did prep create a 512MB swap
> partition when I have 2GB RAM?
prep isn't that smart.
- erik
> to me that looks like a mismatch between fossil's expectations for the
> partition and that actual partition size. i think you're just reading past
> the end of the partition.
Indeed!
su# disk/prep /dev/sdE0/plan9
9fat 0 204800(204800 sectors, 100.00 MB)
nvram
On Sun Oct 16 16:13:58 EDT 2011, slash.9f...@gmail.com wrote:
> > No errors, but I noticed it stopped just before 200 gigabytes.
> I kept reading the disk and got several read errors. Here is the first one:
>
> fossil: diskReadRaw failed: /dev/sdE0/fossil: score 0x016d1389:
> part=data block 23925
Your email does not include the output of disk/prep /dev/sdE0/data.
You have a 1.8TB disk, which has a single DOS partition,
and your fossil sees a 1.8Tb disk, but what size is the
fossil partition? if it was in fact 200Gbytes then this
would explain the problem.
-Steve
> No errors, but I noticed it stopped just before 200 gigabytes.
I kept reading the disk and got several read errors. Here is the first one:
fossil: diskReadRaw failed: /dev/sdE0/fossil: score 0x016d1389:
part=data block 23925641: eof reading disk
Bad sector or something else?
> dd -if /dev/sdE0/fossil -of /dev/null -bs 512k # or whatever partition.
No errors, but I noticed it stopped just before 200 gigabytes. The
total size of the plan9 partition is 1.81 terabytes.
A related question: how should I interpret /dev/sdE0/fossil file size?
# ls -l /dev/sdE0/fossil
--rw-
On Sun Oct 16 11:51:48 EDT 2011, slash.9f...@gmail.com wrote:
> > i've also had trouble with usb disks.
>
> The errors come from sdE0 which is connected to sata port on the
> motherboard. Even when there are no usb disks attached at all.
>
eeeh. sorry.
> I am beginning to think my new disk h
> i've also had trouble with usb disks.
The errors come from sdE0 which is connected to sata port on the
motherboard. Even when there are no usb disks attached at all.
su# cat /dev/sdE0/ctl
inquiry Hitachi HDS5C3020ALA632
model Hitachi HDS5C3020ALA632
serial ML0220FL0220F313JE2D
firm ML6OA5
On Sun Oct 16 10:12:13 EDT 2011, slash.9f...@gmail.com wrote:
> I began consolidating files with great joy from external ext2 disks to
> the new 2 TB fossil drive using trfs.latin1. After only 300 or so
> gigabytes I saw this on the console:
>
> fossil: diskWriteRaw failed: /dev/sdE0/fossil: score
I began consolidating files with great joy from external ext2 disks to
the new 2 TB fossil drive using trfs.latin1. After only 300 or so
gigabytes I saw this on the console:
fossil: diskWriteRaw failed: /dev/sdE0/fossil: score 0x016d1415: data
Sun Oct 16 09:37:58 EDT 2011
part=data block 23925781:
19 matches
Mail list logo
