* reiserfs problem
@ 2001-02-23 17:03 Patrick Mackinlay
2001-02-23 18:31 ` Chris Mason
0 siblings, 1 reply; 4+ messages in thread
From: Patrick Mackinlay @ 2001-02-23 17:03 UTC (permalink / raw)
To: linux-kernel
When 2.4.1 was released I reported a kernel oops with reiserfs, I got no
response.
The problem still persists with kernel 2.4.2. I am using mkreiserfs v2
(3.6.25) and tried on different ide hards disks as well as on a software
raid 0 partition, I also tried with and without CONFIG_REISERFS_CHECK
defined, the oops always happens.
My system is a dual pentium 500, 256M memory, IDE:
IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
The system has been running flawlessly with 2.2 kernels for months.
This is how I caused the first oops:
Created 2Gig reiserfs partition on /dev/md0 (raid0)
mount /dev/md0 /mnt/md0
Mount took 3-5 seconds
cp -ax / /mnt/md0
Only the /bin directory (not the contents!) was copied and then cp core
dumped. syslog reports an oops, however the system is still usable but
mount/umount/sync is not possible on any filesystems.
kernel oops report:
>>EIP; d2cf9db8 <[reiserfs]create_virtual_node+298/490> <=====
Trace; d2cfc053 <[reiserfs]dc_check_balance_leaf+53/150>
Trace; d2cfc975 <[reiserfs]fix_nodes+115/450>
Trace; d2d062ac <[reiserfs]reiserfs_cut_from_item+1fc/430>
Trace; d2d152f0 <[reiserfs]reiserfs_mounted_fs_count+0/4>
Trace; d2d0686e <[reiserfs]reiserfs_do_truncate+32e/470>
Trace; d2d18044 <.bss.end+1165/???
Trace; d2cf8567 <[reiserfs]reiserfs_truncate_file+b7/1a0>
Trace; d2d0fa24 <[reiserfs].rodata.start+11e4/678e>
Trace; d2d141af <[reiserfs].rodata.start+596f/678e>
Trace; d2cf9382 <[reiserfs]reiserfs_file_release+1d2/380>
Trace; d2cf94cf <[reiserfs]reiserfs_file_release+31f/380>
Trace; d2d0fb8c <[reiserfs].rodata.start+134c/678e>
Trace; d2d141af <[reiserfs].rodata.start+596f/678e>
Trace; c0128230 <file_read_actor+0/60>
Trace; c0135e47 <fput+37/e0>
Trace; c0134d56 <filp_close+a6/b0>
Trace; c0134dbb <sys_close+5b/70>
Trace; c0109127 <system_call+33/38>
Code; d2cf9db8 <[reiserfs]create_virtual_node+298/490>
00000000 <_EIP>:
Code; d2cf9db8 <[reiserfs]create_virtual_node+298/490> <=====
0: 8b 40 14 mov 0x14(%eax),%eax <=====
Code; d2cf9dbb <[reiserfs]create_virtual_node+29b/490>
3: ff d0 call *%eax
Code; d2cf9dbd <[reiserfs]create_virtual_node+29d/490>
5: 89 c2 mov %eax,%edx
Code; d2cf9dbf <[reiserfs]create_virtual_node+29f/490>
7: 8b 06 mov (%esi),%eax
Code; d2cf9dc1 <[reiserfs]create_virtual_node+2a1/490>
9: 83 c4 10 add $0x10,%esp
Code; d2cf9dc4 <[reiserfs]create_virtual_node+2a4/490>
c: 01 c2 add %eax,%edx
Code; d2cf9dc6 <[reiserfs]create_virtual_node+2a6/490>
e: 89 16 mov %edx,(%esi)
Code; d2cf9dc8 <[reiserfs]create_virtual_node+2a8/490>
10: 8b 83 8c 01 00 00 mov 0x18c(%ebx),%eax
--
Patrick Mackinlay patrick@spacesurfer.com
ICQ: 59277981 tel: +44 7050699851
fax: +44 7050699852
SpaceSurfer Limited http://www.spacesurfer.com/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: reiserfs problem
2001-02-23 17:03 Patrick Mackinlay
@ 2001-02-23 18:31 ` Chris Mason
2001-02-23 18:40 ` Patrick Mackinlay
0 siblings, 1 reply; 4+ messages in thread
From: Chris Mason @ 2001-02-23 18:31 UTC (permalink / raw)
To: patrick, linux-kernel
On Friday, February 23, 2001 05:03:40 PM +0000 Patrick Mackinlay
<patrick@spacesurfer.com> wrote:
> When 2.4.1 was released I reported a kernel oops with reiserfs, I got no
> response.
Hmmm, don't seem to have any other reiserfs mail from you. Sorry I missed
it.
[ ...]
>
> kernel oops report:
>>> EIP; d2cf9db8 <[reiserfs]create_virtual_node+298/490> <=====
We've had a half dozen or so reports so far of this, almost every time it
has been resolved as a compiler issue, usually an unpatched gcc 2.96. One
user was using 2.95.3, but did not report back if switching to 2.95.2 or
egcs fixed the oops.
Anyway, which compiler did you use to compile the kernel?
-chris
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: reiserfs problem
2001-02-23 18:31 ` Chris Mason
@ 2001-02-23 18:40 ` Patrick Mackinlay
0 siblings, 0 replies; 4+ messages in thread
From: Patrick Mackinlay @ 2001-02-23 18:40 UTC (permalink / raw)
To: Chris Mason; +Cc: linux-kernel
Chris Mason wrote:
>
> On Friday, February 23, 2001 05:03:40 PM +0000 Patrick Mackinlay
> <patrick@spacesurfer.com> wrote:
>
> > When 2.4.1 was released I reported a kernel oops with reiserfs, I got no
> > response.
>
> Hmmm, don't seem to have any other reiserfs mail from you. Sorry I missed
> it.
>
> [ ...]
> >
> > kernel oops report:
> >>> EIP; d2cf9db8 <[reiserfs]create_virtual_node+298/490> <=====
>
> We've had a half dozen or so reports so far of this, almost every time it
> has been resolved as a compiler issue, usually an unpatched gcc 2.96. One
> user was using 2.95.3, but did not report back if switching to 2.95.2 or
> egcs fixed the oops.
>
> Anyway, which compiler did you use to compile the kernel?
>
> -chris
I didn't want to join the kernel mailing list (too much traffic) so I
sent it to the email address suggested on the reiserfs home page. I
guess it didn't get through.
It seems I am in fact using a buggy compiler (damn RedHat 7, forgot I
had upgraded on this machine) I will try re-compiling with another
compiler and let you know if I still have problems.
regards,
Patrick
--
Patrick Mackinlay patrick@spacesurfer.com
ICQ: 59277981 tel: +44 7050699851
fax: +44 7050699852
SpaceSurfer Limited http://www.spacesurfer.com/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: reiserfs problem
[not found] <1208801633.20150514020848@vvo.ru>
@ 2015-05-21 1:45 ` Edward Shishkin
0 siblings, 0 replies; 4+ messages in thread
From: Edward Shishkin @ 2015-05-21 1:45 UTC (permalink / raw)
To: jeffm; +Cc: mikh, ReiserfS development mailing list
Jeff,
it seems we need a sanity check somewhere at
the beginning of the resizer to make sure that the
resulted volume is not larger than 16T.
Could you please take a look?
Thanks,
Edward.
On 05/14/2015 12:08 AM, Sergey Mikhalych wrote:
> Здравствуйте, Эдуард.
>
> Прошу прощения, что отвлекаю, да спросить больше не у кого.
> Суть проблемы: в продакшен сервер добавлены дополнительные 6 дисков. собран рейд6 на
> контроллере, физический партишен добавлен в lvm-группу, но на
> финальной стадии - ошибка при расширении файловой системы.
> Обновил ядро до последнего, собрал из исходников последний
> resize_reiserfs - ситуация не меняется.
>
> resize_reiserfs: bitmap.c:176: reiserfs_bitmap_set_bit: Assertion `bit_number < bm->bm_bit_size' failed.
> Aborted
>
> Запустить на выходных fsck.reiserfs ?
>
> ------------
>
> [root@nika mich]# vgdisplay
> --- Volume group ---
> VG Name fedora
> System ID
> Format lvm2
> Metadata Areas 2
> Metadata Sequence No 5
> VG Access read/write
> VG Status resizable
> MAX LV 0
> Cur LV 2
> Open LV 1
> Max PV 0
> Cur PV 2
> Act PV 2
> VG Size 25.47 TiB
> PE Size 4.00 MiB
> Total PE 6675716
> Alloc PE / Size 6675716 / 25.47 TiB
> Free PE / Size 0 / 0
> VG UUID 7zMHCn-2rM3-DwAf-v4pC-2rTG-POHk-ux8cTq
>
> [root@nika mich]# lvdisplay
> --- Logical volume ---
> LV Path /dev/fedora/root
> LV Name root
> VG Name fedora
> LV UUID Xi8boU-eegJ-w2t4-SiBT-EOxY-9Gt0-ufQaNU
> LV Write Access read/write
> LV Creation host, time localhost, 2014-08-23 05:40:09 +0400
> LV Status available
> # open 1
> LV Size 19.53 GiB
> Current LE 5000
> Segments 1
> Allocation inherit
> Read ahead sectors auto
> - currently set to 256
> Block device 253:0
>
> --- Logical volume ---
> LV Path /dev/fedora/home
> LV Name home
> VG Name fedora
> LV UUID 8u78Jm-tfLO-s0k7-99az-RQVx-cPez-lCX16b
> LV Write Access read/write
> LV Creation host, time localhost, 2014-08-23 05:40:10 +0400
> LV Status available
> # open 0
> LV Size 25.45 TiB
> Current LE 6670716
> Segments 2
> Allocation inherit
> Read ahead sectors auto
> - currently set to 256
> Block device 253:1
>
> [root@nika mich]# pvdisplay
> --- Physical volume ---
> PV Name /dev/sdc4
> VG Name fedora
> PV Size 10.91 TiB / not usable 0
> Allocatable yes (but full)
> PE Size 4.00 MiB
> Total PE 2860805
> Free PE 0
> Allocated PE 2860805
> PV UUID ojkwZA-vSnJ-5L85-HRJA-iGLw-WmdG-1LOK8o
>
> --- Physical volume ---
> PV Name /dev/sdd1
> VG Name fedora
> PV Size 14.55 TiB / not usable 2.98 MiB
> Allocatable yes (but full)
> PE Size 4.00 MiB
> Total PE 3814911
> Free PE 0
> Allocated PE 3814911
> PV UUID zqqnp3-73Cv-u4HW-8r7g-zg03-GsGl-jRG4vM
>
> [root@nika mich]# resize_reiserfs /dev/fedora/home
> resize_reiserfs 3.6.21 (2009 www.namesys.com)
>
> resize_reiserfs: bitmap.c:176: reiserfs_bitmap_set_bit: Assertion `bit_number < bm->bm_bit_size' failed.
> Aborted
>
> [root@nika mich]# mount /home
> [root@nika mich]# df -k
> Filesystem 1K-blocks Used Available Use% Mounted on
> devtmpfs 8192864 0 8192864 0% /dev
> tmpfs 8199908 0 8199908 0% /dev/shm
> tmpfs 8199908 636 8199272 1% /run
> tmpfs 8199908 0 8199908 0% /sys/fs/cgroup
> /dev/mapper/fedora-root 20027260 13954688 5032188 74% /
> tmpfs 8199908 0 8199908 0% /tmp
> /dev/md0 249804944 84018732 165786212 34% /var/lib/mysql
> /dev/mapper/fedora-home 11697377276 10464383528 1232993748 90% /home
>
>
> [root@nika mich]# uname -a
> Linux nika 3.19.5-100.fc20.x86_64 #1 SMP Mon Apr 20 19:51:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>
> [root@nika mich]# mount
> /dev/mapper/fedora-home on /home type reiserfs (rw,noatime)
>
>> Перпезагрузился с nomount опцией, и сразу попробовал удалить партишен
>> из группы:
> [root@nika mich]# pvremove /dev/sdd1 --force --force
> Really WIPE LABELS from physical volume "/dev/sdd1" of volume group "fedora" [y/n]? y
> WARNING: Wiping physical volume label from /dev/sdd1 of volume group "fedora"
> Can't open /dev/sdd1 exclusively - not removing. Mounted filesystem?
>
> [root@nika mich]# fdisk -l
>
> Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0x9509a759
>
> Device Boot Start End Blocks Id System
> /dev/sda1 2048 500118191 250058072 fd Linux raid autodetect
>
>
> Disk /dev/sdb: 238.5 GiB, 256060514304 bytes, 500118192 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0xf34dca6b
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 2048 500118191 250058072 fd Linux raid autodetect
>
>
> Disk /dev/sdc: 10.9 TiB, 12000138625024 bytes, 23437770752 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: gpt
> Disk identifier: 9EA5B48C-FD78-47D5-A677-649084CAEA92
>
> Device Start End Size Type
> /dev/sdc1 2048 4095 1M BIOS boot partition
> /dev/sdc2 4096 1028095 500M Microsoft basic data
> /dev/sdc3 1028096 2052095 500M Linux swap
> /dev/sdc4 2052096 23437768703 10.9T Linux LVM
>
>
> Disk /dev/sdd: 14.6 TiB, 16000900661248 bytes, 31251759104 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 4096 bytes
> I/O size (minimum/optimal): 4096 bytes / 4096 bytes
> Disklabel type: gpt
> Disk identifier: 0DCCB049-2A14-4666-B91C-16DC8EBB0E30
>
> Device Start End Size Type
> /dev/sdd1 2048 31251759070 14.6T Linux LVM
>
>
> Disk /dev/mapper/fedora-root: 19.5 GiB, 20971520000 bytes, 40960000 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
>
> Disk /dev/md0: 238.4 GiB, 255925223424 bytes, 499853952 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
>
> Disk /dev/mapper/fedora-home: 25.5 TiB, 27979010801664 bytes, 54646505472 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 4096 bytes
> I/O size (minimum/optimal): 4096 bytes / 4096 bytes
>
> [root@nika mich]# cat /proc/mdstat
> Personalities : [raid1]
> md0 : active raid1 sdb1[1] sda1[0]
> 249926976 blocks super 1.2 [2/2] [UU]
> bitmap: 0/2 pages [0KB], 65536KB chunk
>
> unused devices: <none>
>
>
> [root@nika MegaCli]# dmsetup info
> Name: fedora-root
> State: ACTIVE
> Read Ahead: 256
> Tables present: LIVE
> Open count: 1
> Event number: 0
> Major, minor: 253, 0
> Number of targets: 1
> UUID: LVM-7zMHCn2rM3DwAfv4pC2rTGPOHkux8cTqXi8boUeegJw2t4SiBTEOxY9Gt0ufQaNU
>
> Name: fedora-home
> State: ACTIVE
> Read Ahead: 256
> Tables present: LIVE
> Open count: 2
> Event number: 0
> Major, minor: 253, 1
> Number of targets: 2
> UUID: LVM-7zMHCn2rM3DwAfv4pC2rTGPOHkux8cTq8u78JmtfLOs0k799azRQVxcPezlCX16b
>
> [root@nika MegaCli]# lvscan
> ACTIVE '/dev/fedora/root' [19.53 GiB] inherit
> ACTIVE '/dev/fedora/home' [25.45 TiB] inherit
>
> [root@nika resize_reiserfs]# ./resize_reiserfs /dev/dm-1
> resize_reiserfs 3.6.24
>
> resize_reiserfs: bitmap.c:176: reiserfs_bitmap_set_bit: Assertion `bit_number < bm->bm_bit_size' failed.
> Aborted
>
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-05-21 1:45 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1208801633.20150514020848@vvo.ru>
2015-05-21 1:45 ` reiserfs problem Edward Shishkin
2001-02-23 17:03 Patrick Mackinlay
2001-02-23 18:31 ` Chris Mason
2001-02-23 18:40 ` Patrick Mackinlay
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.