[Ocfs-users] seg fault using ocfstool

[Sunil Mushran]

ocfstool gets the list of devices from /proc/partitions.
It then reads the first sector from each device to look for the ocfs
signature.

For format, it gives a drop down list of devices for the user to select.
So, if it is formatting /dev/sdc, one must be selecting it. At least I
would hope so. :-)

cat /proc/partitions
may yield some clues.

Sunil

On Tue, 2004-06-29 at 03:40, Roland Zimmermann wrote:
> Hi all,
> 
> i have the following configuration:
> 
> RHAS 2.1 2.4.9-e.40enterprise #1 SMP (2 node cluster).
> 
> ocfs-support-1.1.2-1
> ocfs-tools-1.1.2-1
> ocfs-2.4.9-e-enterprise-1.0.12-1
> 
> i followed the users guide to install and configure ocfs.
> During definition and formatting of ocfs-partitions the ocfstool crashed.
> 
> Now restarting ocfstool fails with the following error:
> 
> ocfstool
> Abnormal termination!
> There may be bound raw devices left lying around, please clean them up
> using the raw(8) command.
> Segmentation fault
> 
> checking with raw -qa returns 1 row:
> [root at chdb100 root]# raw -qa
> /dev/raw/raw1:  bound to major 8, minor 32
> 
> i can unbind it with raw /dev/raw/raw1 0 0 but next execution of 
> ocfstool fails with the same error.
> 
> Here excerpt of strace:
> 2705  munmap(0x4001d000, 4096)          = 0
> 2705  stat64("/dev/sdc", {st_mode=S_IFBLK|0660, st_rdev=makedev(8, 32), 
> ...}) = 0
> 2705  open("/dev/rawctl", O_RDWR)       = 4
> 2705  ioctl(4, RAW_SETBIND, 0xbffecb00) = 0
> 2705  close(4)                          = 0
> 2705  open("/dev/raw/raw1", O_RDONLY)   = 4
> 2705  brk(0x80b8000)                    = 0x80b8000
> 2705  _llseek(4, 0, [0], SEEK_SET)      = 0
> 2705  read(4, 0x80b7000, 512)           = -1 EIO (Input/output error)
> 2705  _llseek(4, 0, [0], SEEK_SET)      = 0
> 2705  read(4, "", 0)                    = 0
> 2705  --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> 2705  write(2, "Abnormal termination!\n", 22) = 22
> 2705  write(2, "There may be bound raw devices l"..., 71) = 71
> 2705  write(2, "using the raw(8) command.\n", 26) = 26
> 2705  rt_sigaction(SIGSEGV, {SIG_DFL}, {0x402f0b30, [SEGV], 
> SA_RESTORER|SA_RESTART, 0x40346988}, 8) = 0
> 2705  kill(2705, SIGSEGV)               = 0
> 2705  sigreturn()                       = ? (mask now [RTMIN])
> 2705  --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> 2705  +++ killed by SIGSEGV +++
> *****
> Indeed 8,32 points to /dev/sdc which is the wrong device, it doesn't 
> exist on this node. The shared device is /dev/sdb.
> 
> Using ocfstool on the other node works fine.
> 
> My question is now: how does ocfstool get the information which device 
> to use (not to mention that i deinstalled and reinstalled ocfs, rebooted 
> the system, deleted ocfs.conf and recreated a new one)  and how can i 
> override those wrong entries?
> 
> Thanks in advance,
> 
> Roland
> 
> _______________________________________________
> Ocfs-users mailing list
> Ocfs-users at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs-users