[Veritas-vx] filesystem corrupted by NBU restore
Duncan Bradey
duncan.bradey at veritas.com
Thu Sep 16 20:44:04 CDT 2004
Hi George,
It looks like something has gone wrong during the restore - possibly
hardware, possibly software related. The reason that you had the problems
with the filesystem is as follows:-
Sep 3 04:32:28 prod2 unix: WARNING: msgcnt 34233 vxfs: mesg 037:
vx_metaioerr - vx_tran_dircompact:1 - /dev/vx/dsk/prod2dg/uat5 file system
meta data write
Sep 3 04:32:28 prod2 unix: error in block 1988784
Sep 3 04:32:29 prod2 unix: WARNING: msgcnt 34234 vxfs: mesg 031: vx_disable
- /dev/vx/dsk/prod2dg/uat5 file system disabled
The filesystem experienced a write error to the metadata and as such
disabled the filesystem, anytime a filesystem gets a write error to the
metadata (filesystem structure) it will be disabled.
I would suggest that you open a case with VERITAS support and have this
investigated - may be too late now, but they may find something.
BTW, for future reference if a filesystem is disabled it will not require a
reboot, just to be umounted, fsck'd and remounted. I would also strongly
suggest that if your filesystem requires a full fsck (with metadata write
errors this is generally the case) then you should open a support case
before running it as in a worst case a full fsck can result in loss of all
files. VERITAS support will be able to walk you through it in the safest
way possible
DISCLAIMER: BUT be aware it is highly recommended that you have a full
backup to fall back on because as good as support is they can not (always
;-) work miracles.
Regards,
Duncan
_____
From: george.done at orangemail.nl [mailto:george.done at orangemail.nl]
Sent: Friday, 17 September 2004 9:17 AM
To: veritas-vx at mailman.eng.auburn.edu
Subject: [Veritas-vx] filesystem corrupted by NBU restore
Dear friends,
I had an issue with a filesystem, /uat5 which was restored, by an user,
using Veritas NetBackup 4.5 while some of the files in it were open by
processes owned by the same user.
What happened is that besides the filesystem has overflowed, it also became
corrupted in such a way thay it could not be "cd" into it, could not be
unmounted, etc. when running "df" was displaying I/O error, etc. The
underlaying volume was started all the time.
The only way to clear the error was to reboot the whole server, after which
the filesystem came clean without any fsck.
While it is normal to expect problems when restoring over open files, is
there a way to clear such error without rebooting the server ?
The filesystem is VXFS 3.5.
Sep 3 04:32:28 prod2 unix: NOTICE: msgcnt 34232 vxfs: mesg 001: vx_nospace
- /dev/vx/dsk/prod2dg/uat5 file system full (1 bl
ock extent)
Sep 3 04:32:28 prod2 unix: WARNING: msgcnt 34233 vxfs: mesg 037:
vx_metaioerr - vx_tran_dircompact:1 - /dev/vx/dsk/prod2dg/u
at5 file system meta data write
Sep 3 04:32:28 prod2 unix: error in block 1988784
Sep 3 04:32:29 prod2 unix: WARNING: msgcnt 34234 vxfs: mesg 031: vx_disable
- /dev/vx/dsk/prod2dg/uat5 file system disabled
Sep 3 04:32:29 prod2 unix: WARNING: msgcnt 34235 vxfs: mesg 017:
vx_tran_dircompact:1 - /uat5 file system inode 9353 marked
bad incore
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34235 offset 0x00000000 800001ff
0 0 0
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34235 offset 0x00000010 0
0 4137d7bc cf316
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34235 offset 0x00000020 4137d7bc
cf316 4137d7bc cf316
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34235 offset 0x00000030 10001
0 352 3e7
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34235 offset 0x00000040 0
643a810b 0 567
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34235 offset 0x00000050 0
0 0 0
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34235 offset 0x00000060 0
0 0 0
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34235 offset 0x00000070 0
0 0 0
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34235 offset 0x00000080 0
0 0 0
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34235 offset 0x00000090 0
0 0 0
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34235 offset 0x000000a0 0
0 0 0
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34235 offset 0x000000b0 0
0
Sep 3 04:32:29 prod2 unix: WARNING: msgcnt 34236 vxfs: mesg 017:
vx_tran_dircompact:2 - /uat5 file system inode 850 marked b
ad incore
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34236 offset 0x00000000 41e8
c 5e1 64
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34236 offset 0x00000010 0
9800 4137084b 3d28d
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34236 offset 0x00000020 4136951b
daddd 4136951b daddd
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34236 offset 0x00000030 10100
0 17 0
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34236 offset 0x00000040 13
1 0 11ae4
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34236 offset 0x00000050 0
0 0 0
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34236 offset 0x00000060 45008
8 45010 8
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34236 offset 0x00000070 45018
3 0 0
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34236 offset 0x00000080 0
0 0 0
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34236 offset 0x00000090 0
0 0 0
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34236 offset 0x000000a0 0
0 0 0
Sep 3 04:32:29 prod2 unix: vxfs msgcnt 34236 offset 0x000000b0 0
0
Met vriendelijke groeten / Kind regards,
George Done
Storage & Unix System Administrator
Orange Nederland N.V.
Tel: +31(0)628026216
Fax: +31(0)648997173
E-mail: <mailto:george.done at orangemail.nl> george.done at orangemail.nl
There is no future in time travel !
===========================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is alleen
bestemd voor de geadresseerde. Indien u dit bericht onterecht ontvangt,
wordt u verzocht de inhoud niet te gebruiken en de afzender direct te
informeren door het bericht te retourneren. Hoewel Orange maatregelen heeft
genomen om virussen in deze email of attachments te voorkomen, dient u ook
zelf na te gaan of virussen aanwezig zijn aangezien Orange niet
aansprakelijk is voor computervirussen die veroorzaakt zijn door deze
email..
The information contained in this message may be confidential and is
intended to be only for the addressee. Should you receive this message
unintentionally, please do not use the contents herein and notify the sender
immediately by return e-mail. Although Orange has taken steps to ensure that
this email and attachments are free from any virus, you do need to verify
the possibility of their existence as Orange can take no responsibility for
any computer virus which might be transferred by way of this email.
===========================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.eng.auburn.edu/pipermail/veritas-vx/attachments/20040917/af4c366d/attachment.html
More information about the Veritas-vx
mailing list