Markus Heller wrote: > > hi all, > > but the error as reported is known to you? i mean, the mount command > saying that there is no valid superblock... >
Standard message. This is because your backup was created on the old reiserfs that probably doesn't support reiserfs journal. New kernels (like in 7.3) don't know this reiserfs format.. > are you sure i didn't do anything wrong? is this a normal error message in > this case? shouldn't the mount command at least say something like ... > "hey, i've found a filesystem, but don't know how to handle it"? Not sure at 100%: you should also look at the kernel messages after failed mount, but I guess it was something like :'can't find reiserfs filesystem'. If your backup is really important, the only way is to build the old kernel you used before upgrade. I think your backup will be accessible again. Edward. > > Markus > (waiting for the disk to be shipped to me currently) > > On Mon, 14 Jan 2002, Edward Shushkin wrote: > > Chris Mason wrote: > > > On Monday, January 14, 2002 05:29:03 PM +0100 Markus Heller <[EMAIL PROTECTED]> > > > wrote: > > > > i have been running a very old kernel (2.2.something). i saved all my > > > > backup data on a reiser partition, did a backup to suse 7.3 and tried to > > > > remount it, without success. the old suse version was 6.3, however with a > > > > newer 2.2 series kernel. i think it was 2.2.18... > > > SuSE 6.3 shipped with the non-journaled version of reiserfs, which can't be > > > read by current reiserfs versions. I wonder if the journal relocation patch > > > could be used to mount the disk. > > Nope. The relocation patch allows to mount all the file systems that are available > > with non-patched kernel plus non-standard ones. > > Edward. > >
