On Thu, Oct 27, 2005 at 10:25:43AM -0700, Chris Marble wrote:
> Jon LaBadie wrote:
> >
> > On Wed, Oct 26, 2005 at 11:53:16AM -0700, Chris Marble wrote:
> > > >
> > > > the /dev/sdb2 is mounted on / partition
> > > > but instead of using /dev/sdb2 it uses /dev/root for backup
> > > > here is the right of the two devices
> > > >
> > > > brw------- 1 root root 8, 18 avr 1 16:48 /dev/root
> > > > brw-rw---- 1 root disk 8, 18 avr 1 16:48 /dev/sdb2
> > >
> > > Did you ever get a solution to this problem? I've done a chgrp disk
> > > and chmod g+r on /dev/root but that only helps until the next reboot.
> > > The other partitions are fine.
> > > Client is 2.4.5 and server is 2.4.4p1
> > > Client OS is CentOS 4.2
> >
> > On my FC3 /dev/root is a symbolic link to the root partition.
> > Might that be persistant across reboot?
> >
> > Under /etc, where I'd expect nearly anything related to devices
> > and booting, the only referenced I find to /dev/root are under
> > /etc/selinux. Do you have secure linux enabled and might there
> > be some setting for that system that is recreating /dev/root?
>
> My /dev/root isn't a sym link but a normal device file. No LVM in use
> either. I'm trying to figure out why amanda's backing up /dev/root instead
> of simply /. Here's the lines from disklist:
> Sakai / comp-root 1
> Sakai /boot comp-root 1
> Sakai /usr/local comp-root 2
> Sakai /var comp-root 2
>
> [10:00am] cmarble@sakai (/dev): ll sda1 sda2 sda root
> brw-r----- 1 root disk 8, 2 Oct 26 04:34 root
> brw-rw---- 1 root disk 8, 0 Oct 26 04:34 sda
> brw-rw---- 1 root disk 8, 1 Oct 26 04:34 sda1
> brw-rw---- 1 root disk 8, 2 Oct 26 04:34 sda2
>
> Lastly lines from sendsize and sendbackup showing successes and failures:
> sendsize.20051026000002.debug:sendsize[3765]: time 0.003: calculating for
> device '/dev/root' with 'ext3'
> sendsize.20051026000002.debug:sendsize[3765]: time 0.003: running "/sbin/dump
> 0Ssf 1048576 - /dev/root"
> sendsize.20051026000002.debug:sendsize[3765]: time 0.028: DUMP: Cannot open
> /dev/root
> sendsize.20051027000002.debug:sendsize[3634]: time 0.007: calculating for
> device '/dev/root' with 'ext3'
> sendsize.20051027000002.debug:sendsize[3634]: time 0.007: running "/sbin/dump
> 0Ssf 1048576 - /dev/root"
> sendbackup.20051027001751.debug:sendbackup: time 0.098: dumping device
> '/dev/root' with 'ext3'
> sendbackup.20051027001751.debug:sendbackup: argument list: dump 0usf 1048576
> - /dev/root
> sendbackup.20051027001751.debug:sendbackup: time 0.104: 93: normal(|):
> DUMP: Dumping /dev/root (an unlisted file system) to standard output
>
> You see that amanda is asking for information on /dev/root rather than simply
> /
My recollection, i.e., I did not check any code,
is that amanda at times needs the directory
and in other places the device. Thus a mapping
of the two is needed. IIRC the mapping is /etc/fstab
for linux. Though I guess it could be the mount table,
either /etc/mnttab (droppings left by the mount command)
and the more reliable, kernel's view of what is mounted
is accessible under /proc/mounts.
What do those 3 sources of information say about your
root file system. Any mentions of /dev/root?
Just as a workaround you might try the device name in
your disklist rather than the starting directory. Amanda
will still have to do some mapping, but it will be
device->directory rather than the current directory->device.
Shouldn't be needed, but might work better in this situation.
--
Jon H. LaBadie jon AT jgcomp DOT com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
