dev_seek error during ufsdump

2007-12-25 0:34:00

Dear Sunmanagers,

Few days ago one of our E3500 systems become to fail its backups with the
following error message:

DUMP: Writing 32 Kilobyte records
DUMP: Date of this level 0 dump: Wed Feb 12 03:38:08 2003
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/vx/rdsk/rootvol (buseoori:/) to /dev/rmt/0hn.
DUMP: Mapping (Pass I) [regular files]
DUMP: Mapping (Pass II) [directories]
DUMP: Estimated 1301400 blocks (635.45MB).
DUMP: Dumping (Pass III) [directories]
DUMP: Dumping (Pass IV) [regular files]
DUMP: bread: dev_seek error: Error 0
<snip>
DUMP: bread: dev_seek error: Error 0
DUMP: Warning - block 1818755308 is beyond the end of
`/dev/vx/rdsk/rootvol'
<snip>
DUMP: Warning - block 1650221670 is beyond the end of
`/dev/vx/rdsk/rootvol'
DUMP: More than 32 block read errors from dump device
`/dev/vx/rdsk/rootvol'
DUMP: bread: dev_seek error: Error 0
DUMP: NEEDS ATTENTION: Do you want to attempt to continue? ("yes" or
"no") DUMP: bread: dev_seek error: Error 0

I searched in the codeprof archives but nobody seemed to have a good
ersponse from their support staff. Also I browsed the sunsolve's archives
but there are theories mainly (that's why I call this site "unsolve" :) )

Our local Sun Support representative quoted the man page that states:

When running ufsdump, the file sys-
tem must be inactive; otherwise, the output of ufsdump may
be inconsistent and restoring files correctly may be impos-
sible. A file system is inactive when it is unmouned or the
system is in single user mode.

Well, the error message shown above was run *in single user mode* as
suggested.

1.- Environment: E3500, Sol 2.6, kernel level: 32, OBP 3.2.29, Volume
Manager 3.1.1 with encapsulated root disk, Veritas Filesystem 3.3.2 for the
rest of filesystems except for root, /var, and /opt.
2.- This backup method had been in use for about three years now.

Any ideas, clues or jokes will be very appreciated.

Many thanks in advance,

- Andres.

Comments

Got something to say?

You must be logged in to post a comment.