btcreate vdump failure on user_domain#users ?

From: Jean Pierre Denis (JeanPierre.Denis_at_pwgsc.gc.ca)
Date: 05/11/04

  • Next message: jreprogle_at_downhill.at.eu.org: "Software"
    Date: Tue, 11 May 2004 10:46:04 -0400
    To: Mailling List - Tru64-unix-managers <tru64-unix-managers@ornl.gov>
    
    

    Hi Tru64 Manger,

     we are trying to do a btcreate backup on 5.1 with the following script:

    --
    #!/bin/sh
    TAPE=/dev/ntape/tape0_d1; export TAPE
    /sbin/mt -f $TAPE rewind
    /usr/sys/bin/btcreate -f -d /users/it -k HOSTNAME -m mfs -s /it/etc/fslist -t $TAPE 
    /sbin/mt -f $TAPE rewind
    --
    The script complete successfully but end with the following errors:
    Dumping the file system user_domain#users of type advfs
    vdump failed for file system user_domain#users.
    The content of /it/etc/fslist is:
    root_domain#root / advfs
    usr_domain#usr /usr advfs
    usr_domain#var /var advfs
    user_domain#users /users advfs
    u0_domain#u0 /u0 advfs
    Could user_domain#users be falling because "-d /users/it" is used as tmp ?
    Beside saying that it failed, btcreate.log doesn't really help to troubleshoot this problem...
    The full btcreate.log file can be reviewed bellow.
    Any help or hint would be great !
    Thanks,
    Jean-Pierre Denis
    Midrange Systems Operations
    Macdonald Cartier Data Centre
    * (613) 998-6435
    * jeanpierre.denis_at_pwgsc.gc.ca
    --
    /var/adm/btcreate.log:
     You have started btcreate as follows :
     /usr/sys/bin/btcreate -f -d /users/it -k HOSTNAME -m mfs -s /it/etc/fslist -t /dev/ntape/tape0_d1
    			BOOTABLE TAPE CREATION
    Veryfying Kernel Configuration file... Done
    Verifying tape...  Done. 
    /it/etc/fslist is of correct file type.
    Entry : root_domain#root / advfs 
    Disklabel checks verified. 
    Entry : root_domain#root / advfs 
    File system checks verified. 
    root_domain#root / advfs selected for back up.
    Entry : usr_domain#usr /usr advfs 
    Disklabel checks verified. 
    Entry : usr_domain#usr /usr advfs 
    File system checks verified. 
    usr_domain#usr /usr advfs selected for back up.
    Entry : usr_domain#var /var advfs 
    Disklabel checks verified. 
    Entry : usr_domain#var /var advfs 
    File system checks verified. 
    usr_domain#var /var advfs selected for back up.
    Entry : user_domain#users /users advfs 
    Disklabel checks verified. 
    Entry : user_domain#users /users advfs 
    File system checks verified. 
    user_domain#users /users advfs selected for back up.
    Entry : u0_domain#u0 /u0 advfs 
    Disklabel checks verified. 
    Entry : u0_domain#u0 /u0 advfs 
    File system checks verified. 
    u0_domain#u0 /u0 advfs selected for back up.
    No files added to the miniroot file system.
    Creating a new kernel...
    Preparing for kernel build in tmp space...
    Creating a new kernel directory /users/it/HOSTNAME.BOOTABLE...
    Creating links to /sys/bin directories...
    Creating link to the tmp space...
    *** KERNEL CONFIGURATION AND BUILD PROCEDURE ***
    Saving /sys/conf/HOSTNAME.BOOTABLE as /sys/conf/HOSTNAME.BOOTABLE.bck
    Do you want to edit the configuration file? (y/n) [n]: 
    *** PERFORMING KERNEL BUILD ***
    	Working....Sun May  9 23:00:28 EDT 2004
    The new kernel is /sys/HOSTNAME.BOOTABLE/vmunix
    Moving the new kernel to /users/it/vmunix.
    vmunix / 40960 mfs tape0_d1 HOSTNAME.BOOTABLE /users/it
    Using mfs; MNT is /var/tmp/cantmp.445880.130.05/mfsmnt451348
    cp: /usr/lib/sabt/sbin/custom_install.sh: No such file or directory
    cp: /usr/lib/sabt/etc/custom_disklabel_file: No such file or directory
    Creating device files on mfs... 
    MAKEDEV: special file(s) for klog: 
    klog 
    MAKEDEV: special file(s) for kcon: 
    kcon 
    MAKEDEV: special file(s) for kbinlog: 
    kbinlog 
    MAKEDEV: special file(s) for kmem: 
    kmem 
    MAKEDEV: special file(s) for mem: 
    mem 
    MAKEDEV: special file(s) for null: 
    null 
    MAKEDEV: special file(s) for vmzcore: 
    vmzcore 
    MAKEDEV: special file(s) for console: 
    console 
    MAKEDEV: special file(s) for ws0: 
    ws0 
    MAKEDEV: special file(s) for mouse0: 
    mouse0 
    MAKEDEV: special file(s) for keyboard0: 
    keyboard0 
    MAKEDEV: special file(s) for tty: 
    tty 
    MAKEDEV: special file(s) for pty0: 
    ptyp0 ttyp0 ptyp1 ttyp1 ptyp2 ttyp2 ptyp3 ttyp3 ptyp4 ttyp4 ptyp5 ttyp5 ptyp6 ttyp6 ptyp7 ttyp7 ptyp8 ttyp8 ptyp9 ttyp9 ptypa ttypa ptypb ttypb ptypc ttypc ptypd ttypd ptype ttype ptypf ttypf 
    MAKEDEV: special file(s) for pty1: 
    ptyq0 ttyq0 ptyq1 ttyq1 ptyq2 ttyq2 ptyq3 ttyq3 ptyq4 ttyq4 ptyq5 ttyq5 ptyq6 ttyq6 ptyq7 ttyq7 ptyq8 ttyq8 ptyq9 ttyq9 ptyqa ttyqa ptyqb ttyqb ptyqc ttyqc ptyqd ttyqd ptyqe ttyqe ptyqf ttyqf 
    MAKEDEV: special file(s) for ptmx: 
    ptmx_bsd ptm 
    MAKEDEV: special file(s) for cam: 
    cam 
    MAKEDEV: special file(s) for audit: 
    audit 
    MAKEDEV: special file(s) for prf: 
    prf 
    MAKEDEV: special file(s) for pfcntr: 
    pfcntr 
    MAKEDEV: special file(s) for zero: 
    zero 
    MAKEDEV: special file(s) for snmpinfo: 
    snmpinfo 
    MAKEDEV: special file(s) for lockdev: 
    lockdev 
    MAKEDEV: special file(s) for sysdev0: 
    sysdev0 
    Getting copy of kernel...
    Merging file system into kernel...
    Merging sboot into kernel...
    pmerge sboot into kernel...
    performing dd...
    performing cat...
    deleting /users/it/vmunix.boot.451348...
    Moving /users/it/vmunix.tmp.451348 to /users/it/vmunix.boot.451348...
    Making tape bootable kernel...
    Writing vmunix...
    Dumping the file system root_domain#root of type advfs
    Dump finished.
    Dumping the file system usr_domain#usr of type advfs
    Dump finished.
    Dumping the file system usr_domain#var of type advfs
    Dump finished.
    Dumping the file system user_domain#users of type advfs
    vdump failed for file system user_domain#users.
    Dumping the file system u0_domain#u0 of type advfs
    Dump finished.
    Rewinding the tape.
    btcreate.log file has been created on /var/adm directory.
    	End of system image creation on tape.
    --
    

  • Next message: jreprogle_at_downhill.at.eu.org: "Software"

    Relevant Pages

    • Re: AdvFS & LSM friends or competitor
      ... But imagine you wished to mirror disks ... > AdvFS is a file system. ... The AdvFS system is journaled so providing ... > AdvFS cannot mirror between its storage systems... ...
      (comp.unix.tru64)
    • SUMMARY Pt II: 100% full filesystem
      ... Subject: SUMMARY: 100% full filesystem ... One is file system boot time checks, ... equivalent to "fsck" in the AdvFS stuff, consistency is sort of assumed as a ... AdvFS, unlike UFS, does indeed have mandatory quota files, even if you are ...
      (Tru64-UNIX-Managers)
    • Re: AdvFS & LSM friends or competitor
      ... AdvFS is a file system, just like any other Unix file system. ... - It's File Domain and Fileset concept make it incredibly flexible. ... Think of a domain as the logical equivalent of a physical disk and a ...
      (comp.unix.tru64)
    • Re: Adfs Filesystem?? Whats That [Re: DoveCot vs Cyrus-Imapd Performance]
      ... > Advfs is Digital's Advanced File System. ... > type of file system than UFS. ... striping, which is done at the file level instead of the block level), ...
      (Fedora)
    • Re: udev/hotplug?
      ... You should be able to get rid of udev by populating a real /dev ... MAKEDEV). ... the dev file system gets mounted on /dev. ...
      (Fedora)