Hi,
I'm trying to restore from a level 0 dump file taken from our samba
server, so the file in question was created by windows.
The dump file is made with the following command:
/sbin/dump -0au -f - /dev/rsd1d | gzip | ssh nirvana.internal 'cd
/backup/dukkha/full/; dd of=shared.gz'
restore is hanging on a file name with some weird characters.
restore > cd Jawnie/SC2007
restore > verbose
verbose mode on
restore > ls
./Jawnie/SC2007:
1834258 ./
1834112 ../
1834490 4582_photo_22200523428PM_Zablocki_Craignewweb.jpg
1834450 April2007.qxp
1834487 Bio.doc
1834480 Carlie07_grey.jpg
1834488 Document Scrap 'C/
Once it prints that last character, restore is frozen. ctrl-c will
bring it back to the restore> prompt from a hung ls, but during extract
I have to kill the xterm itself and then log back in.
ktrace run on the restore pid yields a little more of the filename:
"
11609 restore RET write 27/0x1b
11609 restore CALL write(0x2,0x80147000,0x34)
11609 restore GIO fd 2 wrote 52 bytes
"1834488 Document Scrap '\M-o\M^C\M^X Journal Entrie...'.shs
"
On a console (not xterm) the file name appears to be
Document Scrap 'C/ Journal Entrie...'.shs
(that's a lower case "i" with two dots over it.)
After the ctrl-c, I stop ktrace and this is the last of the kdump.
11609 restore RET write 1
11609 restore CALL sigprocmask(0x1,0)
11609 restore RET sigprocmask 0
11609 restore CALL write(0x2,0x80147000,0xa)
11609 restore GIO fd 2 wrote 10 bytes
"restore > "
11609 restore RET write 10/0xa
11609 restore CALL read(0,0x8ba15000,0x10000)
11609 restore PSIG SIGINT caught handler=0x1c002044 mask=0x0
11609 restore RET read RESTART
11609 restore CALL sigprocmask(0x3,0)
11609 restore RET sigprocmask 2
11609 restore CALL write(0x2,0x80147000,0xa)
11609 restore GIO fd 2 wrote 10 bytes
"restore > "
11609 restore RET write 10/0xa
11609 restore CALL read(0,0x8ba15000,0x10000)
This file is of no consequence other than restore can't proceed beyond
it. In order to continue I added all the files, then used delete Docu*
to remove it from the extract list.
I tried to extract it by the directory and by the inode and restore
hangs either way.
The dump file itself is 15.1 GB uncompressed and 12 GB compressed so I'm
attaching it to this e-mail...just kidding! But I can make it available
if someone needs it--contact me off list.
Thanks,
Jeff Ross
