> -----Original Message-----
> From: Seth Mos [mailto:knuffie@xxxxxxxxx]
> Sent: February 20, 2003 12:28a
> To: l.a walsh; linux-xfs@xxxxxxxxxxx
> Cc: 'Chris Wedgwood'
> Subject: RE: been a while before i could get back to this..
>
>
> At 17:59 19-2-2003 -0800, l.a walsh wrote:
>
> > > Can you tell me what kernel you were running again? Was is
> > > the 1.2 based
> > > release with a bit older dump and restore?
> >
> >linux-2.4.20 (vanilla) with feb 04,04 xfs-all patch
> >
> >xfsdump 2.2.3.
>
> Can you try a newer CVS perhaps. There has been some CVS
> breakage this
> month. You might be affected.
---
I don't have CVS setup.
This problem has existed in its current form since last October.
It's not a recent breakage.
> if /var is seperate partition you might be able to find the
> filesystem
> shutdown message in the /var/log/messages log.
---
Not if var is mounted on "/" or the socket to write to
syslog is under "/"...I setup syslog to record to another system...
These are the local window messages when I tried to dump:
+ xfsdump -b 1048576 -m -l 0 -o -L root - /
+ su -f -m backup -c 'nice -19 bzip2 >root/root-030220-0-2201.dump.bz2'
xfsdump: using file dump (drive_simple) strategy
xfsdump: version 2.2.6 (dump format 3.0) - Running single-threaded
xfsdump: level 0 dump of ishtar:/
xfsdump: dump date: Thu Feb 20 22:01:40 2003
xfsdump: session id: 1dfb2395-0d6c-4132-9ba0-0b41bc30c3c0
xfsdump: session label: "root"
xfsdump: ino map phase 1: skipping (no subtrees specified)
xfsdump: ino map phase 2: constructing initial dump list
xfsdump: WARNING: failed to get bulkstat information for inode 1590
xfsdump: syssgi( SGI_FS_BULKSTAT ) on fsroot failed: Input/output error
xfsdump: Dump Status: ERROR
+ read fs dev DUMP
./dumplin: line 19: read: read error: 0: Input/output error
ishtar:root/bin# ls
bash: /bin/ls: Input/output error
=========
These are the log messages I saw in the remote syslog:
Feb 21 00:12:03 ishtar kernel: xfs_inotobp: xfs_imap() returned an error 22 on
sd(8,3). Returning error.
Feb 21 00:12:03 ishtar kernel: xfs_iunlink_remove: xfs_inotobp() returned an
error 22 on sd(8,3). Returning error.
Feb 21 00:12:03 ishtar kernel: xfs_inactive: xfs_ifree() returned an error =
22 on sd(8,3)
Feb 21 00:12:03 ishtar kernel: xfs_force_shutdown(sd(8,3),0x1) called from line
1835 of file xfs_vnodeops.c. Return address = 0xc0213dca
Feb 21 00:12:03 ishtar kernel: Filesystem "sd(8,3)": I/O Error Detected.
Shutting down filesystem: sd(8,3)
Feb 21 00:12:03 ishtar kernel: Please umount the filesystem, and rectify the
problem(s)
------
I like that last line -- since 'umount' is unavailable...:-/
> cd /tmp
> nohup xfsdump -yada yada &
> this should save at least the xfsdump output. Even if the
> root fs shutdown
> you should still be able to read and write other partitions.
---
I could -- but they are all mounted under "/"....Had the output
going to a file on /tmp, and another window watching that file with
tail -f, nada...after reboot file has 0 len
Hopefully the log above gives some cluese?
|