On Thu, Mar 18, 2004 at 01:26:02PM +1030, Greg 'groggy' Lehey wrote:
> On Tuesday, 16 March 2004 at 17:25:26 +0000, Lewis Thompson wrote:
> > I can't think of anything else.  Originally I ran dd without the
> > conv=noerror and it stopped at around 25GB (the disk is a 100GB).  The
> > destination disk is 123GB but to my knowledge that is acceptable for dd.
> >
> >   During the process a number (maybe eight to ten) I/O errors were
> > reported. 
> 
> But not to me.

I've included more detailed errors neared to the end of this email :)

> I was really thinking of "What to do if you have problems with Vinum"
> at http://www.vinumvm.org/vinum/how-to-debug.html.

Okay, I did actually do my best to follow this but maybe got
sidetracked.  I'm just going to bullet point these now so I don't miss
any of them out.

* Problems: ``dd'' cloned disk ``does not work'' (i.e. gstat shows no
  activity on the cloned disk during reading of files).  Also see
  previous emails.

* Version: FreeBSD 5.2.1-p1.

* Changes to system: Originally vinum ran on 4.9-STABLE.  This worked
  but had periodic ``disk crashes'' (i.e. vinum states disk as offline).
  I don't think this is the problem as the same behaviour happens with
  5.2.1-p1 using the original dodgy disk (only GEOM removes it instead
  of vinum).

* Vinum list (excuse lack of wrapping).  vinumdrive2/ad3 is the cloned
  disk.  The failed volume is data (I don't think you need the others
  but I'll leave them, just in case ;):

vinum -> list
3 drives:
D vinumdrive2           State: up       /dev/ad3s1h     A: 0/95558 MB (0%)
D vinumdrive1           State: up       /dev/ad2s1h     A: 0/117246 MB (0%)
D vinumdrive0           State: up       /dev/ad1s1h     A: 0/117246 MB (0%)

5 volumes:
V root                  State: up       Plexes:       2 Size:        255 MB
V swap                  State: up       Plexes:       2 Size:        459 MB
V var                   State: up       Plexes:       2 Size:        256 MB
V usr                   State: up       Plexes:       2 Size:         12 GB
V data                  State: up       Plexes:       1 Size:        295 GB

9 plexes:
P root.p0             C State: up       Subdisks:     1 Size:        255 MB
P root.p1             C State: up       Subdisks:     1 Size:        255 MB
P swap.p0             C State: up       Subdisks:     1 Size:        459 MB
P swap.p1             C State: up       Subdisks:     1 Size:        459 MB
P var.p0              C State: up       Subdisks:     1 Size:        256 MB
P var.p1              C State: up       Subdisks:     1 Size:        256 MB
P usr.p0              C State: up       Subdisks:     1 Size:         12 GB
P usr.p1              C State: up       Subdisks:     1 Size:         12 GB
P data.p0             C State: up       Subdisks:     3 Size:        295 GB

11 subdisks:
S root.p0.s0            State: up       D: vinumdrive0  Size:        255 MB
S root.p1.s0            State: up       D: vinumdrive1  Size:        255 MB
S swap.p0.s0            State: up       D: vinumdrive0  Size:        459 MB
S swap.p1.s0            State: up       D: vinumdrive1  Size:        459 MB
S var.p0.s0             State: up       D: vinumdrive0  Size:        256 MB
S var.p1.s0             State: up       D: vinumdrive1  Size:        256 MB
S usr.p0.s0             State: up       D: vinumdrive0  Size:         12 GB
S usr.p1.s0             State: up       D: vinumdrive1  Size:         12 GB
S data.p0.s0            State: up       D: vinumdrive0  Size:        100 GB
S data.p0.s1            State: up       D: vinumdrive1  Size:        100 GB
S data.p0.s2            State: up       D: vinumdrive2  Size:         93 GB

* Vinum history.  I mounted the volume (which was not unmounted properly
  -- fsck took place first) and watched a few films.  Eventually I
  stumbled across one that didn't even start.
  I am certain vinum isn't reading anything from ad3 -- gstat during
  fsck showed *NO* activity on ad3/vinumdrive2:

19 Mar 2004 02:46:38.668561 *** vinum started ***
19 Mar 2004 02:46:39.266076 list 
19 Mar 2004 02:56:23.538633 *** vinum started ***

* /var/log/messages extract.  I originally started vinum a long while
  before, I included this entry too (excuse wrapping):

Mar 17 23:33:57 amnesia kernel: vinum: loaded
Mar 17 23:34:00 amnesia kernel: vinum: reading configuration from /dev/ad1s1h
Mar 17 23:34:00 amnesia kernel: vinum: updating configuration from /dev/ad2s1h
Mar 17 23:34:00 amnesia kernel: vinum: updating configuration from /dev/ad3s1h
Mar 19 02:49:26 amnesia kernel: WARNING: /mnt/data was not properly dismounted
Mar 19 02:52:15 amnesia kernel: vinum: null rqg

  This seems a little odd to me -- previously I had not had a null rqg
error.  I think maybe I didn't test it enough.  Since these are mostly
avi files I can tell if they are broken on not by seeing if they have an
index -- last time they all played but many without indexes.  Nothing
has changed since then; maybe I wasn't being thorough enough?

* Crash dump: No.

*** End of how-to-debug ***

> >   During the process a number (maybe eight to ten) I/O errors were
> > reported. 

These were dd errors.  I didn't write these down at the time (silly of
me) and I'm not sure they even go into any log files.  However, I have
found the exact error messages I got (although the offsets are wrong).
If required I will re-run dd and provide the full errors.

  The messages were:

dd: reading `/dev/ad3': Input/output error
4401038+1 records in
4401038+1 records out

and then I got dropped to a prompt.  Only when I specified the extra
option conv=noerror did dd continue.  Of course I still received these
I/O errors but dd just ignored them.

In a reply to my original question you stated that ``dd if=ad3 of=ad1
bs=8192 conv=noerror'' ``may or may not work, depending on details you
haven't reported.''  Do these detailed errors help at all?  I just read
a thread[1] about dd that makes me wonder whether it would have been.


  I think that's everything.  I'm just going to include some other stuff
from earlier emails that has been chopped earlier.  Maybe it has some
relevance:

= fsck_ufs /dev/vinum/data gives the following message:
= ** /dev/vinum/data
= cannot alloc 4316869296 bytes for inphead

  Thanks very much for taking the time to look at this!

-lewiz.

P.S.
Sorry for the URL wrapping and the horrendous quoting ;)

[1]
http://groups.google.com/groups?q=dd+io+error&start=10&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=doeh0vsq84nmopqeo2n2tu606ic2maaov6%404ax.com&rnum=14

-- 
I was so much older then, I'm younger than that now.  --Bob Dylan, 1964.
------------------------------------------------------------------------
-| msn:[EMAIL PROTECTED] | jabber:[EMAIL PROTECTED] | url:www.lewiz.org |-

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to