Samba / md0_raid1 OpenSuse 11.1

English Network/Internet
#1

Hello,

i have a problem with my samba server on OpenSuse 11.1.
The complete server is hanging completly every day.
You can do nothing with mouse or keyboard, only a complete hardwarereset helps.

In the messages.log or log.smbd are no error-messages.

I logged yesterday with ‘top -b > op.log’ all processes and found the smbd-process on 100-percent CPU.

After some tests the same error occured today,too. I can only ping the server, no ssh-login is possible, but i had a ssh-window with “top” open.

It’s very interesting, CPU for smbd is 100% and running, but md0_raid1/mdadm is on status D.

I couldn’t kill the SMBD-Process. I stopped samba, no success, kill -9, no success.

A few minutes later the server was not reachable.

Do you think it’s a problem with the RAID1?
I installed the server one week, ago. The two hard disks in the raid1 are complete new.

I have three hard discs:
SCSI sda

SATA sdb /sdc → RAID1
with:
MD0 /
MD1 SWAP
MD2 /SAMBA (data)

Boot disc is sdb.

Should i deactivate sdb and start with sdc?

Have someone an idea?
Problem is i’m at the moment not in the office and i must first restart the server there that i can send some logs. Give it for the MD-tools extra logs or only what you can see in the messages file?

Thank you very much
regards
Martin

 

top - 17:02:08 up 1 day,  7:31,  2 users,  load average: 6.00, 5.70, 5.00
Tasks:  90 total,   4 running,  85 sleeping,   1 stopped,   0 zombie
Cpu(s):  0.0%us, 51.5%sy,  0.0%ni,  0.0%id, 48.5%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   2049524k total,  2013352k used,    36172k free,   136024k buffers
Swap:  4192944k total,       44k used,  4192900k free,  1638044k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 4158 root      20   0 17032 4888 3692 R  100  0.2   1565:21 smbd
  651 root      15  -5     0    0    0 D    2  0.0  15:13.12 md0_raid1
 7917 root      20   0  2056  744  640 D    1  0.0   0:00.02 mdadm
 7891 root      20   0 57648  29m  13m S    0  1.5   0:01.71 y2base
    1 root      20   0  1008  356  308 S    0  0.0   0:01.86 init
    2 root      15  -5     0    0    0 S    0  0.0   0:00.00 kthreadd
    3 root      RT  -5     0    0    0 S    0  0.0   0:00.00 migration/0
    4 root      15  -5     0    0    0 S    0  0.0   0:00.50 ksoftirqd/0
    5 root      RT  -5     0    0    0 S    0  0.0   0:00.00 migration/1
    6 root      15  -5     0    0    0 S    0  0.0   0:00.20 ksoftirqd/1
    7 root      15  -5     0    0    0 R    0  0.0   0:00.40 events/0
    8 root      15  -5     0    0    0 S    0  0.0   0:04.04 events/1
    9 root      15  -5     0    0    0 S    0  0.0   0:00.00 khelper
   10 root      15  -5     0    0    0 S    0  0.0   0:00.00 kintegrityd/0
   11 root      15  -5     0    0    0 S    0  0.0   0:00.00 kintegrityd/1
   12 root      15  -5     0    0    0 R    0  0.0   0:00.72 kblockd/0
   13 root      15  -5     0    0    0 S    0  0.0   0:00.16 kblockd/1
#2

On Sat January 10 2009 11:26 am, martin1981er wrote:

>
> Hello,
>
> i have a problem with my samba server on OpenSuse 11.1.
> The complete server is hanging completly every day.
> You can do nothing with mouse or keyboard, only a complete
> hardwarereset helps.
>
> In the messages.log or log.smbd are no error-messages.
>
> I logged yesterday with ‘top -b > op.log’ all processes and found the
> smbd-process on 100-percent CPU.
>
<snip>
Martin;

This may be the broken inotify kernel module
see (particularly the response of Volker):
http://www.mail-archive.com/samba%40lists.samba.org/msg98069.html
and also:
https://bugzilla.novell.com/show_bug.cgi?id=463372

Does this fit your problem?

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

#3

Thanks for your answer, i installed kernel kernel-pae-2.6.27.10-7.1 at the afternoon and added the parameter
notify:inotify = false
in the smb.conf. Shold we have no problems, i will remove the parameter and try it only with the new kernel.

I will give feedback the next days.

regards
Martin

#4

Until now no problems.I removed the notify:inotify = false-parameter at monday evening.

The problem was only the BUG in the old Kernel.
Thanks for your help

#5

On Wed January 14 2009 12:36 pm, martin1981er wrote:

>
> Until now no problems.I removed the notify:inotify = false-parameter at
> monday evening.
>
> The problem was only the BUG in the old Kernel.
> Thanks for your help
>
>
Your welcome, but only by chance did I know about the kernel bug.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green