ADSM-L

Symbolic link problems

1997-03-04 01:47:18
Subject: Symbolic link problems
From: Trevor Foley <Trevor.Foley AT BANKERSTRUST.COM DOT AU>
Date: Tue, 4 Mar 1997 16:47:18 +1000
Trevor Foley
04/03/97 16:47
From:
On:

Hi,

There have been a few steams in the past few days discussing problems with
symbolic links. We are also having problems. The details below were
provided by our Unix support people. Any comments or suggestions would be
appreciated.


regards,

Trevor

---------------------------------------------------------------------------
---
---
In the example environment I have a filesystem "/blah" which contains
In the example environment I have a filesystem "/blah" which contains
the following files:
---------------------------------------------------------------------------
---
---
total 16
total 16
br----S---   1 root     sys        0,  0 Mar 04 14:31 FBLK
cr--------   1 root     sys        0,  0 Mar 04 14:31 FCHR
pr--------   1 root     sys            0 Mar 04 14:31 FIFO
sr----S---   1 root     sys            0 Mar 04 14:31 SOCK
drwxr-s---   2 root     sys          512 Mar 04 15:19 d1
-rw-r-----   1 root     sys            3 Mar 04 14:22 f1
lrwxrwxrwx   1 root     sys            2 Mar 04 15:22 linktodir -> d1
lrwxrwxrwx   1 root     sys            2 Mar 04 15:22 linktodir -> d1
lrwxrwxrwx   1 root     sys            0 Mar 04 15:22 linktoempty ->
lrwxrwxrwx   1 root     sys            2 Mar 04 15:22 linktof1 -> f1
lrwxrwxrwx   1 root     sys           10 Mar 04 15:20 linktonothing ->
/fresh/air

./d1:
total 8
-rw-r-----   1 root     sys            3 Mar 04 14:23 f1
---------------------------------------------------------------------------
---------------------------------------------------------------------------
---
---
This is backed up using the command:
This is backed up using the command:

---------------------------------------------------------------------------
---
---
# dsmc i /blah -subdir=yes -follow=yes -verbose
# dsmc i /blah -subdir=yes -follow=yes -verbose
ADSTAR Distributed Storage Manager
Command Line Backup Client Interface - Version 2, Release 1, Level 0.6
(C) Copyright IBM Corporation, 1990, 1996, All Rights Reserved.

Session established with server AUADSM01: AIX-RS/6000
  Server Version 2, Release 1, Level 5.12
  Data compression forced off by the server
  Server date/time: 03/04/97   15:25:51   Last access: 03/04/97   15:16:47

Incremental backup of file system: '/blah'
Directory-->               512 /blah/d1  Sent
Normal File-->               3 /blah/f1  Sent
Symbolic Link-->             2 /blah/linktodir  Sent
Symbolic Link-->             0 /blah/linktoempty  Sent
Symbolic Link-->             2 /blah/linktof1  Sent
Symbolic Link-->            10 /blah/linktonothing  Sent
Normal File-->               3 /blah/d1/f1  Sent
Successful incremental backup of '/blah'


Total number of objects inspected:       12
Total number of objects backed up:        7
Total number of objects updated:          0
Total number of objects rebound:          0
Total number of objects deleted:          0
Total number of objects failed:           0
Total number of bytes transferred:       70
Average file size:                        6
Elapsed processing time:           00:00:00
---------------------------------------------------------------------------
---
---
All block special, character special, socket files or fifo (pipes) files
All block special, character special, socket files or fifo (pipes) files
were not backed up. Though it appears the symbolic links were backed up
correctly, it is not possible to restore them correctly.

These files were restored with:

---------------------------------------------------------------------------
---
---
# dsmc restore /blah -subdir=true -follow=no /blah2
# dsmc restore /blah -subdir=true -follow=no /blah2
ADSTAR Distributed Storage Manager
Command Line Backup Client Interface - Version 2, Release 1, Level 0.6
(C) Copyright IBM Corporation, 1990, 1996, All Rights Reserved.

ANS4098I Specified directory branch structure has been restored

Total number of objects restored:         6
Total number of bytes transferred:       44
Total failures:                           0
Elapsed processing time:           00:00:00
---------------------------------------------------------------------------
---
---
if an ls -lR is done in this directory you can see what has been restored
if an ls -lR is done in this directory you can see what has been restored

---------------------------------------------------------------------------
---
---
total 16
total 16
drwxr-s---   2 root     sys          512 Mar 04 15:19 d1
-rw-r-----   1 root     sys            3 Mar 04 14:22 f1
lrwxrwxrwx   1 root     bin            0 Mar 04 15:41 linktodir ->
lrwxrwxrwx   1 root     bin            0 Mar 04 15:41 linktodir ->
lrwxrwxrwx   1 root     bin            0 Mar 04 15:41 linktoempty ->
lrwxrwxrwx   1 root     bin            0 Mar 04 15:41 linktof1 ->
lrwxrwxrwx   1 root     bin            0 Mar 04 15:41 linktonothing ->

./d1:
total 8
-rw-r-----   1 root     sys            3 Mar 04 14:23 f1
---------------------------------------------------------------------------
---------------------------------------------------------------------------
---
---
sadly, symbolic links point to fresh air and special files are gone.
sadly, symbolic links point to fresh air and special files are gone.

same result if you supply:

-follow=yes
to the restore command.
to the restore command.

So we have 2 main issues:

 1. ADSM cannot cope with special files (block,character,pipes,sockets).

 2. ADSM does not restore symbolic links correctly. It just restores
    links which don't point anywhere. eg  "symlink -> "
<Prev in Thread] Current Thread [Next in Thread>