-
Hi Carsten,
thanks a lot for the research you did there!! And welcome to the hell of cross-distro development :-) blkid is just another example of nasty changes that are not really announced anywhere.
The philosophy of ReaR is to recover the system as close to the original as possible. With regard to filesystem create we still are not perfect because we do not copy all the special...
2010-01-07 20:45:11 UTC by schlomoschapiro
-
BTW, I just committed the fix to trunk, in case you want to check it out (try contrib/svn2host ...)
2010-01-07 20:34:17 UTC by schlomoschapiro
-
Aaaarghhhhhhh! I was so sure that I tested this also on SLES9!!!
Yes, it is a bug. We will fix it with the next ReaR release. In the mean time you could also install the vol_id RPM we provide on https://sourceforge.net/projects/rear/files/vol_id/SLES9SP3 ...
Sorry about that,
Schlomo
PS: As a quick workaround you could of course change the line with the test to read
elif type -p...
2010-01-07 20:06:52 UTC by schlomoschapiro
-
Hi Schlomo,
I did some research regarding the grub problem and it developed something like this: at some point the maintainer of the e2fsprogs decided to change the default inode size of mkfs from 128 to 256 to be prepared for the coming ext4. Unfortunatly grub 0.97 couldn't work with 256 byte inodes. Grub wasn't able to load stage1 if the stage1 file was stored on a file system with 256 byte...
2010-01-07 15:23:28 UTC by crshh
-
Hi Schlomo,
I've checked the SLES9 installation and it doesn't have the udev_volume_id function and neither does it have the vol_id function.
The test
type -p blkid >/dev/null && ! type -p udev_volume_id >/dev/null
returns 0.
The output of the command blkid has the same structure on SLES9 and SLES10, but on both systems the parameter "udev" for the "-o " option is unknown.
So, the reason...
2010-01-07 14:26:39 UTC by crshh
-
Hi Carsten,
I thought I checked the blkid stuff on my SLES9...
In http://rear.svn.sourceforge.net/viewvc/rear/releases/1.7.23/usr/share/rear/lib/compatibility-functions.sh?view=markup I use a negative check for udev_volume_id to cover the SLES9 case which should make ReaR use the builtin vol_id function. The check looks like this:
type -p blkid >/dev/null && ! type -p udev_volume_id...
2010-01-06 15:05:43 UTC by schlomoschapiro
-
Hi Carsten,
you indeed found a sore point with ReaR, which is the fact that it does not (yet) recover any advanced file system properties. The correct way to fix this is to add somethting to http://rear.svn.sourceforge.net/viewvc/rear/releases/1.7.23/usr/share/rear/dr/GNU/Linux/12_describe_filesystems.sh?view=markup which records more information into the fs_vol_id file and then add something...
2010-01-06 15:01:59 UTC by schlomoschapiro
-
Hi,
I've a SLES9 Installation with a customized kernel (for the lustre file system). I've installed Rear 1.7.23 from the tar archive and I wanted to create a PXE output via NETFS.
After "rear -s mkbackup" or "rear -s mkrescue" the following message appears:
"ERROR: BUG BUG BUG! Incompatible 'blkid' on this system.
Please report this as a bug to the authors of Relax & Recover".
2010-01-06 14:42:42 UTC by crshh
-
Hi,
I have a SuSE Linux Enterprise 10 SP2 installation and I've installed ReaR from the tar file. There was no problem with mkbackup or with booting the rescue system, I've used output PXE and backup NETFS.
But the recovered system could not boot, because the grub installation failed and I even couldn't install grub manually later on.
Error message in rear.log was:
grub> setup...
2010-01-06 13:18:04 UTC by crshh
-
schlomoschapiro made 2 file-release changes.
2009-12-11 09:33:01 UTC by schlomoschapiro
