* Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine
@ 2004-09-24 3:20 Chris Worley
2004-09-24 7:17 ` Vitaly Fertman
0 siblings, 1 reply; 12+ messages in thread
From: Chris Worley @ 2004-09-24 3:20 UTC (permalink / raw)
To: reiserfs-list
I have a similar problem to:
On 2004-07-15 13:06:46 Vitaly Fertman Wrote:
> Hello,
>
> >...
> >
> > Boot --> please use fsck manualy on /
>
> what version of reiserfsck are you using? please update
> reiserfsprogs to the latest one from our ftp site.
>
I'm using 3.6.13... which version do you propose?
> ...
I'm getting the same error where the ReiserFS root partition won't fsck,
but seems otherwise fine:
I "fixed" it by replacing /sbin/mkfs.reiserfs with a script that always
returns true... now the system boots fine ;)
It's a Reiser fs atop an LVM block device of one partition. The problem
started when I switched from lilo to grub... that could be irrelevant.
Once booted, Reiser still doesn't even recognize the root file system (I
saved the executable in fsck.reiserfs.bak):
# /sbin/fsck.reiserfs.bak /dev/system/lvol0
reiserfsck 3.6.13 (2003 www.namesys.com)
*************************************************************
** If you are using the latest reiserfsprogs and it fails **
** please email bug reports to reiserfs-list@namesys.com, **
** providing as much information as possible -- your **
** hardware, kernel, patches, settings, all reiserfsck **
** messages (including version), the reiserfsck logfile, **
** check the syslog file for any related information. **
** If you would like advice on using this program, support **
** is available for $25 at www.namesys.com/support.html. **
*************************************************************
Will read-only check consistency of the filesystem on /dev/system/lvol0
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
Failed to open the device '/dev/system/lvol0': No such device or address
Aborted
Note: I'm running a fully patched 9.1. I've been able to use this
fsck.reiserfs to examine other LVM based file systems that were created
under previous LVM and ReiserFS versions. The volume is currently only
made up of /dev/hda3. Both the lvm block device and reiser format were
created under SuSE9.1 (before patching). LVM has no problems:
# pvscan
PV /dev/hda3 VG system lvm2 [226.25 GB / 0 free]
PV /dev/hdd1 lvm2 [233.76 GB]
Total: 2 [460.01 GB] / in use: 1 [226.25 GB] / in no VG: 1 [233.76 GB]
# vgdisplay
--- Volume group ---
VG Name system
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 2
VG Access read/write
VG Status resizable
MAX LV 255
Cur LV 1
Open LV 1
Max PV 255
Cur PV 1
Act PV 1
VG Size 226.25 GB
PE Size 4.00 MB
Total PE 57921
Alloc PE / Size 57921 / 226.25 GB
Free PE / Size 0 / 0
VG UUID glCBN4-xLPB-eGJO-4YVO-p4Hj-ZRMW-LFvJfJ
# lvdisplay
--- Logical volume ---
LV Name /dev/system/lvol0
VG Name system
LV UUID j9z3cd-hY3R-4unM-UwZs-BXVZ-WMJN-iMIvXF
LV Write Access read/write
LV Status available
# open 2
LV Size 226.25 GB
Current LE 57921
Segments 1
Allocation next free (default)
Read ahead sectors 0
Block device 254:0
# pvdisplay
--- Physical volume ---
PV Name /dev/hda3
VG Name system
PV Size 226.25 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 57921
Free PE 0
Allocated PE 57921
PV UUID wQnbCq-FQT9-76gh-HjFP-kBi3-7lE8-psDnAj
--- NEW Physical volume ---
PV Name /dev/hdd1
VG Name
PV Size 233.76 GB
Allocatable NO
PE Size (KByte) 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID lZ0dSs-FR6O-i7fo-z5xZ-APMR-CcBq-Fmm425
# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/system-lvol0
237237168 141678036 95559132 60% /
tmpfs 517676 0 517676 0% /dev/shm
/dev/hda1 38856 18321 18529 50% /boot
Other than fsck, there's no other hint that something is wrong with this
partition.
If this partition were at the beginning of the disk (and not 8GB into
the disk) I'd think grub had destroyed something beyond the MBR... but
this is too far into the disk.
Any idea what's wrong with this root partition and what I could do to
recover it?
Thanks,
Chris
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine
2004-09-24 3:20 SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine Chris Worley
@ 2004-09-24 7:17 ` Vitaly Fertman
2004-09-24 13:20 ` Chris Worley
0 siblings, 1 reply; 12+ messages in thread
From: Vitaly Fertman @ 2004-09-24 7:17 UTC (permalink / raw)
To: Chris Worley, reiserfs-list
On Friday 24 September 2004 07:20, Chris Worley wrote:
> I have a similar problem to:
>
> On 2004-07-15 13:06:46 Vitaly Fertman Wrote:
> > Hello,
> >
> > >...
> > >
> > > Boot --> please use fsck manualy on /
> >
> > what version of reiserfsck are you using? please update
> > reiserfsprogs to the latest one from our ftp site.
>
> I'm using 3.6.13... which version do you propose?
the latest is 3.6.18 (ftp.namesys.com/pub/reiserfsprogs/)
try it please.
> > ...
>
> I'm getting the same error where the ReiserFS root partition won't fsck,
> but seems otherwise fine:
>
> I "fixed" it by replacing /sbin/mkfs.reiserfs with a script that always
> returns true... now the system boots fine ;)
>
> It's a Reiser fs atop an LVM block device of one partition. The problem
> started when I switched from lilo to grub... that could be irrelevant.
>
> Once booted, Reiser still doesn't even recognize the root file system (I
> saved the executable in fsck.reiserfs.bak):
>
> # /sbin/fsck.reiserfs.bak /dev/system/lvol0
> reiserfsck 3.6.13 (2003 www.namesys.com)
>
> *************************************************************
> ** If you are using the latest reiserfsprogs and it fails **
> ** please email bug reports to reiserfs-list@namesys.com, **
> ** providing as much information as possible -- your **
> ** hardware, kernel, patches, settings, all reiserfsck **
> ** messages (including version), the reiserfsck logfile, **
> ** check the syslog file for any related information. **
> ** If you would like advice on using this program, support **
> ** is available for $25 at www.namesys.com/support.html. **
> *************************************************************
>
> Will read-only check consistency of the filesystem on
> /dev/system/lvol0 Will put log info to 'stdout'
>
> Do you want to run this program?[N/Yes] (note need to type Yes if
> you do):Yes
>
> Failed to open the device '/dev/system/lvol0': No such device or
> address
>
> Aborted
>
> Note: I'm running a fully patched 9.1. I've been able to use this
> fsck.reiserfs to examine other LVM based file systems that were created
> under previous LVM and ReiserFS versions. The volume is currently only
> made up of /dev/hda3. Both the lvm block device and reiser format were
> created under SuSE9.1 (before patching). LVM has no problems:
>
> # pvscan
> PV /dev/hda3 VG system lvm2 [226.25 GB / 0 free]
> PV /dev/hdd1 lvm2 [233.76 GB]
> Total: 2 [460.01 GB] / in use: 1 [226.25 GB] / in no VG: 1
> [233.76 GB] # vgdisplay
> --- Volume group ---
> VG Name system
> System ID
> Format lvm2
> Metadata Areas 1
> Metadata Sequence No 2
> VG Access read/write
> VG Status resizable
> MAX LV 255
> Cur LV 1
> Open LV 1
> Max PV 255
> Cur PV 1
> Act PV 1
> VG Size 226.25 GB
> PE Size 4.00 MB
> Total PE 57921
> Alloc PE / Size 57921 / 226.25 GB
> Free PE / Size 0 / 0
> VG UUID glCBN4-xLPB-eGJO-4YVO-p4Hj-ZRMW-LFvJfJ
> # lvdisplay
> --- Logical volume ---
> LV Name /dev/system/lvol0
> VG Name system
> LV UUID j9z3cd-hY3R-4unM-UwZs-BXVZ-WMJN-iMIvXF
> LV Write Access read/write
> LV Status available
> # open 2
> LV Size 226.25 GB
> Current LE 57921
> Segments 1
> Allocation next free (default)
> Read ahead sectors 0
> Block device 254:0
> # pvdisplay
> --- Physical volume ---
> PV Name /dev/hda3
> VG Name system
> PV Size 226.25 GB / not usable 0
> Allocatable yes (but full)
> PE Size (KByte) 4096
> Total PE 57921
> Free PE 0
> Allocated PE 57921
> PV UUID wQnbCq-FQT9-76gh-HjFP-kBi3-7lE8-psDnAj
>
> --- NEW Physical volume ---
> PV Name /dev/hdd1
> VG Name
> PV Size 233.76 GB
> Allocatable NO
> PE Size (KByte) 0
> Total PE 0
> Free PE 0
> Allocated PE 0
> PV UUID lZ0dSs-FR6O-i7fo-z5xZ-APMR-CcBq-Fmm425
> # df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/mapper/system-lvol0
> 237237168 141678036 95559132 60% /
> tmpfs 517676 0 517676 0% /dev/shm
> /dev/hda1 38856 18321 18529 50% /boot
>
> Other than fsck, there's no other hint that something is wrong with this
> partition.
>
> If this partition were at the beginning of the disk (and not 8GB into
> the disk) I'd think grub had destroyed something beyond the MBR... but
> this is too far into the disk.
>
> Any idea what's wrong with this root partition and what I could do to
> recover it?
>
> Thanks,
>
> Chris
--
Thanks,
Vitaly Fertman
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine
2004-09-24 7:17 ` Vitaly Fertman
@ 2004-09-24 13:20 ` Chris Worley
2004-09-24 13:30 ` Hendrik Visage
2004-09-27 14:44 ` Vitaly Fertman
0 siblings, 2 replies; 12+ messages in thread
From: Chris Worley @ 2004-09-24 13:20 UTC (permalink / raw)
To: reiserfs-list
On Fri, 2004-09-24 at 01:17, Vitaly Fertman wrote:
> On Friday 24 September 2004 07:20, Chris Worley wrote:
> > I have a similar problem to:
> >
> > On 2004-07-15 13:06:46 Vitaly Fertman Wrote:
> > > Hello,
> > >
> > > >...
> > > >
> > > > Boot --> please use fsck manualy on /
> > >
> > > what version of reiserfsck are you using? please update
> > > reiserfsprogs to the latest one from our ftp site.
> >
> > I'm using 3.6.13... which version do you propose?
>
> the latest is 3.6.18 (ftp.namesys.com/pub/reiserfsprogs/)
> try it please.
Same result:
# ./fsck/reiserfsck /dev/system/lvol0
reiserfsck 3.6.18 (2003 www.namesys.com)
*************************************************************
** If you are using the latest reiserfsprogs and it fails **
**... **
*************************************************************
Will read-only check consistency of the filesystem on /dev/system/lvol0
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes if you
do):Yes
Failed to open the device '/dev/system/lvol0': No such device or address
Aborted
Note that I am building reiserfs statically in the kernel (SuSE's
2.6.5-52-bigsmp).
Thanks,
Chris
>
> > > ...
> >
> > I'm getting the same error where the ReiserFS root partition won't fsck,
> > but seems otherwise fine:
> >
> > I "fixed" it by replacing /sbin/mkfs.reiserfs with a script that always
> > returns true... now the system boots fine ;)
> >
> > It's a Reiser fs atop an LVM block device of one partition. The problem
> > started when I switched from lilo to grub... that could be irrelevant.
> >
> > Once booted, Reiser still doesn't even recognize the root file system (I
> > saved the executable in fsck.reiserfs.bak):
> >
> > # /sbin/fsck.reiserfs.bak /dev/system/lvol0
> > reiserfsck 3.6.13 (2003 www.namesys.com)
> >
> > *************************************************************
> > ** If you are using the latest reiserfsprogs and it fails **
> > ** please email bug reports to reiserfs-list@namesys.com, **
> > ** providing as much information as possible -- your **
> > ** hardware, kernel, patches, settings, all reiserfsck **
> > ** messages (including version), the reiserfsck logfile, **
> > ** check the syslog file for any related information. **
> > ** If you would like advice on using this program, support **
> > ** is available for $25 at www.namesys.com/support.html. **
> > *************************************************************
> >
> > Will read-only check consistency of the filesystem on
> > /dev/system/lvol0 Will put log info to 'stdout'
> >
> > Do you want to run this program?[N/Yes] (note need to type Yes if
> > you do):Yes
> >
> > Failed to open the device '/dev/system/lvol0': No such device or
> > address
> >
> > Aborted
> >
> > Note: I'm running a fully patched 9.1. I've been able to use this
> > fsck.reiserfs to examine other LVM based file systems that were created
> > under previous LVM and ReiserFS versions. The volume is currently only
> > made up of /dev/hda3. Both the lvm block device and reiser format were
> > created under SuSE9.1 (before patching). LVM has no problems:
> >
> > # pvscan
> > PV /dev/hda3 VG system lvm2 [226.25 GB / 0 free]
> > PV /dev/hdd1 lvm2 [233.76 GB]
> > Total: 2 [460.01 GB] / in use: 1 [226.25 GB] / in no VG: 1
> > [233.76 GB] # vgdisplay
> > --- Volume group ---
> > VG Name system
> > System ID
> > Format lvm2
> > Metadata Areas 1
> > Metadata Sequence No 2
> > VG Access read/write
> > VG Status resizable
> > MAX LV 255
> > Cur LV 1
> > Open LV 1
> > Max PV 255
> > Cur PV 1
> > Act PV 1
> > VG Size 226.25 GB
> > PE Size 4.00 MB
> > Total PE 57921
> > Alloc PE / Size 57921 / 226.25 GB
> > Free PE / Size 0 / 0
> > VG UUID glCBN4-xLPB-eGJO-4YVO-p4Hj-ZRMW-LFvJfJ
> > # lvdisplay
> > --- Logical volume ---
> > LV Name /dev/system/lvol0
> > VG Name system
> > LV UUID j9z3cd-hY3R-4unM-UwZs-BXVZ-WMJN-iMIvXF
> > LV Write Access read/write
> > LV Status available
> > # open 2
> > LV Size 226.25 GB
> > Current LE 57921
> > Segments 1
> > Allocation next free (default)
> > Read ahead sectors 0
> > Block device 254:0
> > # pvdisplay
> > --- Physical volume ---
> > PV Name /dev/hda3
> > VG Name system
> > PV Size 226.25 GB / not usable 0
> > Allocatable yes (but full)
> > PE Size (KByte) 4096
> > Total PE 57921
> > Free PE 0
> > Allocated PE 57921
> > PV UUID wQnbCq-FQT9-76gh-HjFP-kBi3-7lE8-psDnAj
> >
> > --- NEW Physical volume ---
> > PV Name /dev/hdd1
> > VG Name
> > PV Size 233.76 GB
> > Allocatable NO
> > PE Size (KByte) 0
> > Total PE 0
> > Free PE 0
> > Allocated PE 0
> > PV UUID lZ0dSs-FR6O-i7fo-z5xZ-APMR-CcBq-Fmm425
> > # df
> > Filesystem 1K-blocks Used Available Use% Mounted on
> > /dev/mapper/system-lvol0
> > 237237168 141678036 95559132 60% /
> > tmpfs 517676 0 517676 0% /dev/shm
> > /dev/hda1 38856 18321 18529 50% /boot
> >
> > Other than fsck, there's no other hint that something is wrong with this
> > partition.
> >
> > If this partition were at the beginning of the disk (and not 8GB into
> > the disk) I'd think grub had destroyed something beyond the MBR... but
> > this is too far into the disk.
> >
> > Any idea what's wrong with this root partition and what I could do to
> > recover it?
> >
> > Thanks,
> >
> > Chris
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine
2004-09-24 13:20 ` Chris Worley
@ 2004-09-24 13:30 ` Hendrik Visage
2004-09-24 13:56 ` Chris Worley
2004-09-27 14:44 ` Vitaly Fertman
1 sibling, 1 reply; 12+ messages in thread
From: Hendrik Visage @ 2004-09-24 13:30 UTC (permalink / raw)
To: Chris Worley; +Cc: reiserfs-list
1) Why do you *want* to fsck a reiserfs? Unless you have troubles, then a
fsck on a reiserfs is not needed by design of a logging/journaling fs
2) any fsck needs to be done on a read-only mounted fs, and then if
anything have been fixed, that fs preferably needs to be umounted (see the
trouble with / already mounted) and mounted again to makesure the caches etc.
is cleared.
Hendrik
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine
2004-09-24 13:30 ` Hendrik Visage
@ 2004-09-24 13:56 ` Chris Worley
2004-09-24 14:32 ` Hendrik Visage
0 siblings, 1 reply; 12+ messages in thread
From: Chris Worley @ 2004-09-24 13:56 UTC (permalink / raw)
To: reiserfs-list
On Fri, 2004-09-24 at 07:30, Hendrik Visage wrote:
> 1) Why do you *want* to fsck a reiserfs? Unless you have troubles, then a
> fsck on a reiserfs is not needed by design of a logging/journaling fs
You don't have a choice on the root file system... fsck will be run.
Once booted, I am just running a ro fsck of / (on a rw mounted file
system).
If there's really nothing wrong with the FS, then I'm okay just making a
no-op fsck.reiserfs and leaving it at that... I'm just worried that
something is really wrong with the file system, and I need to fix that.
As it sits atop an LVM, I want to add a few more partitions to the LVM
and extend the Reiser fs... but I'm paranoid, with this error, to
proceed.
> 2) any fsck needs to be done on a read-only mounted fs,
Which is the state when fsck is run during boot. I get the same error
when booting and dropping into fsck mode as I do after the system is
booted.
> and then if
> anything have been fixed, that fs preferably needs to be umounted (see the
> trouble with / already mounted) and mounted again to makesure the caches etc.
> is cleared.
If the Reiser tools would just recognize this as a fs, I'd be satisfied.
Thanks,
Chris
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine
2004-09-24 13:56 ` Chris Worley
@ 2004-09-24 14:32 ` Hendrik Visage
2004-09-24 14:58 ` Chris Worley
0 siblings, 1 reply; 12+ messages in thread
From: Hendrik Visage @ 2004-09-24 14:32 UTC (permalink / raw)
To: Chris Worley; +Cc: reiserfs-list
On Fri, Sep 24, 2004 at 07:56:31AM -0600, Chris Worley wrote:
> On Fri, 2004-09-24 at 07:30, Hendrik Visage wrote:
> > 1) Why do you *want* to fsck a reiserfs? Unless you have troubles, then a
> > fsck on a reiserfs is not needed by design of a logging/journaling fs
>
> You don't have a choice on the root file system... fsck will be run.
Then ignore it for a reiserfs...
> If there's really nothing wrong with the FS, then I'm okay just making a
> no-op fsck.reiserfs and leaving it at that... I'm just worried that
> something is really wrong with the file system, and I need to fix that.
> As it sits atop an LVM, I want to add a few more partitions to the LVM
> and extend the Reiser fs... but I'm paranoid, with this error, to
> proceed.
First understand a logging/journaling fs :)
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine
2004-09-24 14:32 ` Hendrik Visage
@ 2004-09-24 14:58 ` Chris Worley
0 siblings, 0 replies; 12+ messages in thread
From: Chris Worley @ 2004-09-24 14:58 UTC (permalink / raw)
To: Hendrik Visage; +Cc: reiserfs-list
On Fri, 2004-09-24 at 08:32, Hendrik Visage wrote:
> On Fri, Sep 24, 2004 at 07:56:31AM -0600, Chris Worley wrote:
> > On Fri, 2004-09-24 at 07:30, Hendrik Visage wrote:
> > > 1) Why do you *want* to fsck a reiserfs? Unless you have troubles, then a
> > > fsck on a reiserfs is not needed by design of a logging/journaling fs
> >
> > You don't have a choice on the root file system... fsck will be run.
>
> Then ignore it for a reiserfs...
>
> > If there's really nothing wrong with the FS, then I'm okay just making a
> > no-op fsck.reiserfs and leaving it at that... I'm just worried that
> > something is really wrong with the file system, and I need to fix that.
> > As it sits atop an LVM, I want to add a few more partitions to the LVM
> > and extend the Reiser fs... but I'm paranoid, with this error, to
> > proceed.
>
> First understand a logging/journaling fs :)
I do understand a journaling fs, and have used Reiser for many years.
My understanding of journaling fs's is not the problem. There was a
time when this fs properly fsck'd at boot, and then a time when it
didn't. This is a problem. Furthermore, SuSE would not have forced the
fsck (irrespective of the fstab settings) of the root fs if it didn't
apply to Reiser.
Please re-read my original email, as I don't think you understand the
situation.
Thanks,
Chris
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine
2004-09-24 13:20 ` Chris Worley
2004-09-24 13:30 ` Hendrik Visage
@ 2004-09-27 14:44 ` Vitaly Fertman
2004-09-27 16:06 ` Chris Worley
1 sibling, 1 reply; 12+ messages in thread
From: Vitaly Fertman @ 2004-09-27 14:44 UTC (permalink / raw)
To: Chris Worley, reiserfs-list
> # ./fsck/reiserfsck /dev/system/lvol0
> reiserfsck 3.6.18 (2003 www.namesys.com)
>
> Failed to open the device '/dev/system/lvol0': No such device or address
it seems
open ('/dev/system/lvol0', O_RDONLY);
returns "No such device or address". You can check it with strace.
what if you run
reiserfsck /dev/mapper/system-lvol0
> Note that I am building reiserfs statically in the kernel (SuSE's
> 2.6.5-52-bigsmp).
>
> > > > ...
> > >
> > > I'm getting the same error where the ReiserFS root partition won't
> > > fsck, but seems otherwise fine:
> > >
> > > I "fixed" it by replacing /sbin/mkfs.reiserfs with a script that always
> > > returns true... now the system boots fine ;)
> > >
> > > It's a Reiser fs atop an LVM block device of one partition. The
> > > problem started when I switched from lilo to grub... that could be
> > > irrelevant.
> > >
> > > Once booted, Reiser still doesn't even recognize the root file system
> > > (I saved the executable in fsck.reiserfs.bak):
> > >
> > > # /sbin/fsck.reiserfs.bak /dev/system/lvol0
> > > reiserfsck 3.6.13 (2003 www.namesys.com)
> > >
> > > Failed to open the device '/dev/system/lvol0': No such device
> > > or address
> > >
> > > Note: I'm running a fully patched 9.1. I've been able to use this
> > > fsck.reiserfs to examine other LVM based file systems that were created
> > > under previous LVM and ReiserFS versions. The volume is currently only
> > > made up of /dev/hda3. Both the lvm block device and reiser format were
> > > created under SuSE9.1 (before patching). LVM has no problems:
have you got this problem just after moving to this kernel
(SuSE's 2.6.5-52-bigsmp)? or upgrading the lvm tools?
the problem is likely to be somewhere in lvm code.
> > > # pvscan
> > > PV /dev/hda3 VG system lvm2 [226.25 GB / 0 free]
> > > PV /dev/hdd1 lvm2 [233.76 GB]
> > > Total: 2 [460.01 GB] / in use: 1 [226.25 GB] / in no VG: 1
> > > [233.76 GB] # vgdisplay
> > > --- Volume group ---
> > > VG Name system
> > > System ID
> > > Format lvm2
> > > Metadata Areas 1
> > > Metadata Sequence No 2
> > > VG Access read/write
> > > VG Status resizable
> > > MAX LV 255
> > > Cur LV 1
> > > Open LV 1
> > > Max PV 255
> > > Cur PV 1
> > > Act PV 1
> > > VG Size 226.25 GB
> > > PE Size 4.00 MB
> > > Total PE 57921
> > > Alloc PE / Size 57921 / 226.25 GB
> > > Free PE / Size 0 / 0
> > > VG UUID glCBN4-xLPB-eGJO-4YVO-p4Hj-ZRMW-LFvJfJ
> > > # lvdisplay
> > > --- Logical volume ---
> > > LV Name /dev/system/lvol0
> > > VG Name system
> > > LV UUID j9z3cd-hY3R-4unM-UwZs-BXVZ-WMJN-iMIvXF
> > > LV Write Access read/write
> > > LV Status available
> > > # open 2
> > > LV Size 226.25 GB
> > > Current LE 57921
> > > Segments 1
> > > Allocation next free (default)
> > > Read ahead sectors 0
> > > Block device 254:0
> > > # pvdisplay
> > > --- Physical volume ---
> > > PV Name /dev/hda3
> > > VG Name system
> > > PV Size 226.25 GB / not usable 0
> > > Allocatable yes (but full)
> > > PE Size (KByte) 4096
> > > Total PE 57921
> > > Free PE 0
> > > Allocated PE 57921
> > > PV UUID wQnbCq-FQT9-76gh-HjFP-kBi3-7lE8-psDnAj
> > >
> > > --- NEW Physical volume ---
> > > PV Name /dev/hdd1
> > > VG Name
> > > PV Size 233.76 GB
> > > Allocatable NO
> > > PE Size (KByte) 0
> > > Total PE 0
> > > Free PE 0
> > > Allocated PE 0
> > > PV UUID lZ0dSs-FR6O-i7fo-z5xZ-APMR-CcBq-Fmm425
> > > # df
> > > Filesystem 1K-blocks Used Available Use% Mounted
> > > on /dev/mapper/system-lvol0
> > > 237237168 141678036 95559132 60% /
> > > tmpfs 517676 0 517676 0%
> > > /dev/shm /dev/hda1 38856 18321 18529 50% /boot
> > >
> > > Other than fsck, there's no other hint that something is wrong with
> > > this partition.
> > >
> > > If this partition were at the beginning of the disk (and not 8GB into
> > > the disk) I'd think grub had destroyed something beyond the MBR... but
> > > this is too far into the disk.
> > >
> > > Any idea what's wrong with this root partition and what I could do to
> > > recover it?
> > >
> > > Thanks,
> > >
> > > Chris
--
Thanks,
Vitaly Fertman
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine
2004-09-27 14:44 ` Vitaly Fertman
@ 2004-09-27 16:06 ` Chris Worley
2004-09-27 22:16 ` evilninja
0 siblings, 1 reply; 12+ messages in thread
From: Chris Worley @ 2004-09-27 16:06 UTC (permalink / raw)
To: Vitaly Fertman; +Cc: reiserfs-list
On Mon, 2004-09-27 at 08:44, Vitaly Fertman wrote:
> > # ./fsck/reiserfsck /dev/system/lvol0
> > reiserfsck 3.6.18 (2003 www.namesys.com)
> >
> > Failed to open the device '/dev/system/lvol0': No such device or address
>
> it seems
> open ('/dev/system/lvol0', O_RDONLY);
> returns "No such device or address". You can check it with strace.
>
> what if you run
> reiserfsck /dev/mapper/system-lvol0
The strace dies on the open:
...
open("/dev/mapper/system-lvol0", O_RDONLY|O_LARGEFILE) = -1 ENXIO (No such device or address)
...
Not even dd can open it:
# dd if=/dev/mapper/system-lvol0 bs=1024 count=1024 | sum
dd: opening `/dev/mapper/system-lvol0': No such device or address
Yet, it exists:
# ls -l /dev/mapper/system-lvol0
brw------- 1 root root 253, 1 Sep 20 15:49 /dev/mapper/system-lvol0
And is the mounted root file system:
# df /
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/system-lvol0
237237168 142041808 95195360 60% /
This makes it look more like a kernel problem. I'm using SuSE's
2.6.5-52-bigsmp, although I built it myself to make some
hand-tweaks to the video driver... and I did statically build in
Reiser to negate the need for an initrd. My kernel reiser
settings are:
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
The LVM settings are as documented before.
It works fine, it just isn't there???
Thanks,
Chris
>
> > Note that I am building reiserfs statically in the kernel (SuSE's
> > 2.6.5-52-bigsmp).
> >
> > > > > ...
> > > >
> > > > I'm getting the same error where the ReiserFS root partition won't
> > > > fsck, but seems otherwise fine:
> > > >
> > > > I "fixed" it by replacing /sbin/mkfs.reiserfs with a script that always
> > > > returns true... now the system boots fine ;)
> > > >
> > > > It's a Reiser fs atop an LVM block device of one partition. The
> > > > problem started when I switched from lilo to grub... that could be
> > > > irrelevant.
> > > >
> > > > Once booted, Reiser still doesn't even recognize the root file system
> > > > (I saved the executable in fsck.reiserfs.bak):
> > > >
> > > > # /sbin/fsck.reiserfs.bak /dev/system/lvol0
> > > > reiserfsck 3.6.13 (2003 www.namesys.com)
> > > >
> > > > Failed to open the device '/dev/system/lvol0': No such device
> > > > or address
> > > >
> > > > Note: I'm running a fully patched 9.1. I've been able to use this
> > > > fsck.reiserfs to examine other LVM based file systems that were created
> > > > under previous LVM and ReiserFS versions. The volume is currently only
> > > > made up of /dev/hda3. Both the lvm block device and reiser format were
> > > > created under SuSE9.1 (before patching). LVM has no problems:
>
> have you got this problem just after moving to this kernel
> (SuSE's 2.6.5-52-bigsmp)? or upgrading the lvm tools?
> the problem is likely to be somewhere in lvm code.
>
> > > > # pvscan
> > > > PV /dev/hda3 VG system lvm2 [226.25 GB / 0 free]
> > > > PV /dev/hdd1 lvm2 [233.76 GB]
> > > > Total: 2 [460.01 GB] / in use: 1 [226.25 GB] / in no VG: 1
> > > > [233.76 GB] # vgdisplay
> > > > --- Volume group ---
> > > > VG Name system
> > > > System ID
> > > > Format lvm2
> > > > Metadata Areas 1
> > > > Metadata Sequence No 2
> > > > VG Access read/write
> > > > VG Status resizable
> > > > MAX LV 255
> > > > Cur LV 1
> > > > Open LV 1
> > > > Max PV 255
> > > > Cur PV 1
> > > > Act PV 1
> > > > VG Size 226.25 GB
> > > > PE Size 4.00 MB
> > > > Total PE 57921
> > > > Alloc PE / Size 57921 / 226.25 GB
> > > > Free PE / Size 0 / 0
> > > > VG UUID glCBN4-xLPB-eGJO-4YVO-p4Hj-ZRMW-LFvJfJ
> > > > # lvdisplay
> > > > --- Logical volume ---
> > > > LV Name /dev/system/lvol0
> > > > VG Name system
> > > > LV UUID j9z3cd-hY3R-4unM-UwZs-BXVZ-WMJN-iMIvXF
> > > > LV Write Access read/write
> > > > LV Status available
> > > > # open 2
> > > > LV Size 226.25 GB
> > > > Current LE 57921
> > > > Segments 1
> > > > Allocation next free (default)
> > > > Read ahead sectors 0
> > > > Block device 254:0
> > > > # pvdisplay
> > > > --- Physical volume ---
> > > > PV Name /dev/hda3
> > > > VG Name system
> > > > PV Size 226.25 GB / not usable 0
> > > > Allocatable yes (but full)
> > > > PE Size (KByte) 4096
> > > > Total PE 57921
> > > > Free PE 0
> > > > Allocated PE 57921
> > > > PV UUID wQnbCq-FQT9-76gh-HjFP-kBi3-7lE8-psDnAj
> > > >
> > > > --- NEW Physical volume ---
> > > > PV Name /dev/hdd1
> > > > VG Name
> > > > PV Size 233.76 GB
> > > > Allocatable NO
> > > > PE Size (KByte) 0
> > > > Total PE 0
> > > > Free PE 0
> > > > Allocated PE 0
> > > > PV UUID lZ0dSs-FR6O-i7fo-z5xZ-APMR-CcBq-Fmm425
> > > > # df
> > > > Filesystem 1K-blocks Used Available Use% Mounted
> > > > on /dev/mapper/system-lvol0
> > > > 237237168 141678036 95559132 60% /
> > > > tmpfs 517676 0 517676 0%
> > > > /dev/shm /dev/hda1 38856 18321 18529 50% /boot
> > > >
> > > > Other than fsck, there's no other hint that something is wrong with
> > > > this partition.
> > > >
> > > > If this partition were at the beginning of the disk (and not 8GB into
> > > > the disk) I'd think grub had destroyed something beyond the MBR... but
> > > > this is too far into the disk.
> > > >
> > > > Any idea what's wrong with this root partition and what I could do to
> > > > recover it?
> > > >
> > > > Thanks,
> > > >
> > > > Chris
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine
2004-09-27 16:06 ` Chris Worley
@ 2004-09-27 22:16 ` evilninja
2004-09-27 22:40 ` Chris Worley
0 siblings, 1 reply; 12+ messages in thread
From: evilninja @ 2004-09-27 22:16 UTC (permalink / raw)
To: reiserfs-list; +Cc: Chris Worley
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chris Worley wrote:
> On Mon, 2004-09-27 at 08:44, Vitaly Fertman wrote:
>
>>># ./fsck/reiserfsck /dev/system/lvol0
>>>reiserfsck 3.6.18 (2003 www.namesys.com)
>>>
>>>Failed to open the device '/dev/system/lvol0': No such device or address
>>
>>it seems
>> open ('/dev/system/lvol0', O_RDONLY);
>>returns "No such device or address". You can check it with strace.
>>
>>what if you run
>> reiserfsck /dev/mapper/system-lvol0
>
>
>
> The strace dies on the open:
>
> ...
> open("/dev/mapper/system-lvol0", O_RDONLY|O_LARGEFILE) = -1 ENXIO (No such device or address)
> ...
>
> Not even dd can open it:
>
> # dd if=/dev/mapper/system-lvol0 bs=1024 count=1024 | sum
> dd: opening `/dev/mapper/system-lvol0': No such device or address
ah, now this is funny. dd doesn't care about the filesystem and can't even
read the device. this does not seem like a (reiser-)fs issue, more like a
corrupted partition table / device (if the data on
/dev/mapper/system-lvol0 is not (!) important, you could play around with
$ mkfs.{ext3|xfs|reiserfs} /dev/mapper/system-lvol0
and see what it gives. (probably won't work too)
good luck,
Christian.
- --
BOFH excuse #180:
ether leak
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBWI5oC/PVm5+NVoYRAhM1AJ9Vwr+oX8Z7SaiRqzK5TPDn2tnS3gCg7K3K
VFq2Eped9ceUjbCWyOi+/+k=
=qVnK
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine
2004-09-27 22:16 ` evilninja
@ 2004-09-27 22:40 ` Chris Worley
2004-09-29 0:38 ` evilninja
0 siblings, 1 reply; 12+ messages in thread
From: Chris Worley @ 2004-09-27 22:40 UTC (permalink / raw)
To: evilninja; +Cc: reiserfs-list
On Mon, 2004-09-27 at 16:16, evilninja wrote:
> ah, now this is funny. dd doesn't care about the filesystem and can't even
> read the device.
> this does not seem like a (reiser-)fs issue, more like a
> corrupted partition table / device
I agree that it's not a reiser issue... but, how did it get mounted in
the first place?
> (if the data on
> /dev/mapper/system-lvol0 is not (!) important, you could play around with
I find the root partition an invaluable part of the system. So, I'm not
going to destroy it on purpose. I'm not quite sure how to boot without
a root partition ;)
I'm really looking for a non-destructive way to test/repair whatever has
happened. The partitioning seems fine (an ext3 boot directory of a few
MB, an 8GB swap, and the root partition):
Device Boot Start End Blocks Id System
/dev/hda1 * 1 5 40131 83 Linux
/dev/hda2 6 979 7823655 82 Linux swap
/dev/hda3 980 30515 237247920 8e Linux LVM
Chris
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine
2004-09-27 22:40 ` Chris Worley
@ 2004-09-29 0:38 ` evilninja
0 siblings, 0 replies; 12+ messages in thread
From: evilninja @ 2004-09-29 0:38 UTC (permalink / raw)
To: reiserfs-list
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chris Worley wrote:
> I find the root partition an invaluable part of the system. So, I'm not
> going to destroy it on purpose. I'm not quite sure how to boot without
> a root partition ;)
you did backup at least /etc , didn't you? if so, then a quick reinstall
of your distro (and thus overwriting "/" ) should be not that painful.
> I'm really looking for a non-destructive way to test/repair whatever has
> happened.
well, there's always http://www.namesys.com/support.html ;)
Christian.
- --
BOFH excuse #71:
The file system is full of it
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBWgQDC/PVm5+NVoYRApvLAKCXAWCz3PrDzLehnrTBEUeIGtwFWACgkIdh
wr4EZlLE0y76Srjny9Bt8Qw=
=i5O+
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2004-09-29 0:38 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-24 3:20 SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine Chris Worley
2004-09-24 7:17 ` Vitaly Fertman
2004-09-24 13:20 ` Chris Worley
2004-09-24 13:30 ` Hendrik Visage
2004-09-24 13:56 ` Chris Worley
2004-09-24 14:32 ` Hendrik Visage
2004-09-24 14:58 ` Chris Worley
2004-09-27 14:44 ` Vitaly Fertman
2004-09-27 16:06 ` Chris Worley
2004-09-27 22:16 ` evilninja
2004-09-27 22:40 ` Chris Worley
2004-09-29 0:38 ` evilninja
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.