All of lore.kernel.org
 help / color / mirror / Atom feed
* [Ocfs2-devel] OCFS2 errors in log EVEN just after FSCK
@ 2015-06-24  7:15 vde at ykoctpa.ru
  2015-06-25  1:28 ` Joseph Qi
  0 siblings, 1 reply; 2+ messages in thread
From: vde at ykoctpa.ru @ 2015-06-24  7:15 UTC (permalink / raw)
  To: ocfs2-devel

There is 2-node cluster with master-master DRBD and OCFS2 filesystem, kernel 
4.0.4

Some time ago I found such errors in log (on both nodes)

Jun 24 06:43:05 node1 kernel: [31704.810029] (php-
fpm,30917,1):ocfs2_orphan_del:2331 ERROR: status = -2
Jun 24 06:43:05 node1 kernel: [31704.810034] (php-
fpm,30917,1):ocfs2_orphan_del:2362 ERROR: status = -2
Jun 24 06:43:05 node1 kernel: [31704.810037] (php-
fpm,30917,1):ocfs2_remove_inode:653 ERROR: status = -2
Jun 24 06:43:05 node1 kernel: [31704.810041] (php-
fpm,30917,1):ocfs2_wipe_inode:798 ERROR: status = -2
Jun 24 06:43:05 node1 kernel: [31704.810044] (php-
fpm,30917,1):ocfs2_delete_inode:1050 ERROR: status = -2
Jun 24 06:44:27 node1 o2hbmonitor: mount debugfs at /sys/kernel/debug
Jun 24 06:45:09 node1 kernel: [31828.939394] 
(kworker/u8:1,25619,1):ocfs2_orphan_del:2331 ERROR: status = -2
Jun 24 06:45:09 node1 kernel: [31828.939399] 
(kworker/u8:1,25619,1):ocfs2_orphan_del:2362 ERROR: status = -2
Jun 24 06:45:09 node1 kernel: [31828.939402] 
(kworker/u8:1,25619,1):ocfs2_remove_inode:653 ERROR: status = -2
Jun 24 06:45:09 node1 kernel: [31828.939406] 
(kworker/u8:1,25619,1):ocfs2_wipe_inode:798 ERROR: status = -2
Jun 24 06:45:09 node1 kernel: [31828.939409] 
(kworker/u8:1,25619,1):ocfs2_delete_inode:1050 ERROR: status = -2
Jun 24 06:45:09 node1 kernel: [31828.943074] 
(kworker/u8:1,25619,1):ocfs2_orphan_del:2331 ERROR: status = -2
Jun 24 06:45:09 node1 kernel: [31828.943078] 
(kworker/u8:1,25619,1):ocfs2_orphan_del:2362 ERROR: status = -2
Jun 24 06:45:09 node1 kernel: [31828.943081] 
(kworker/u8:1,25619,1):ocfs2_remove_inode:653 ERROR: status = -2
Jun 24 06:45:09 node1 kernel: [31828.943084] 
(kworker/u8:1,25619,1):ocfs2_wipe_inode:798 ERROR: status = -2
Jun 24 06:45:09 node1 kernel: [31828.943087] 
(kworker/u8:1,25619,1):ocfs2_delete_inode:1050 ERROR: status = -2
Jun 24 06:45:09 node1 kernel: [31828.951077]  
(kworker/u8:1,25619,1):ocfs2_orphan_del:2331 ERROR: status = -2
Jun 24 06:45:09 node1 kernel: [31828.951081] 
(kworker/u8:1,25619,1):ocfs2_orphan_del:2362 ERROR: status = -2
Jun 24 06:45:09 node1 kernel: [31828.951083] 
(kworker/u8:1,25619,1):ocfs2_remove_inode:653 ERROR: status = -2
Jun 24 06:45:09 node1 kernel: [31828.951087] 
(kworker/u8:1,25619,1):ocfs2_wipe_inode:798 ERROR: status = -2
Jun 24 06:45:09 node1 kernel: [31828.951089] 
(kworker/u8:1,25619,1):ocfs2_delete_inode:1050 ERROR: status = -2

and so on. FSCK (ocfs2_tools 1.8.4) every time found and fix lots of "orphaned 
cluster" errors but after mount this starts again.

in namei.c I found that this starts from ocfs2_find_entry  - so there is some 
filesystem errors leaved even after fsck 

WBR,
Dmitry V.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Ocfs2-devel] OCFS2 errors in log EVEN just after FSCK
  2015-06-24  7:15 [Ocfs2-devel] OCFS2 errors in log EVEN just after FSCK vde at ykoctpa.ru
@ 2015-06-25  1:28 ` Joseph Qi
  0 siblings, 0 replies; 2+ messages in thread
From: Joseph Qi @ 2015-06-25  1:28 UTC (permalink / raw)
  To: ocfs2-devel

It seems that it cannot find entry in ocfs2_orphan_del.
Could you please check if commit e38a573907 is involved in your kernel
version?

On 2015/6/24 15:15, vde at ykoctpa.ru wrote:
> There is 2-node cluster with master-master DRBD and OCFS2 filesystem, kernel 
> 4.0.4
> 
> Some time ago I found such errors in log (on both nodes)
> 
> Jun 24 06:43:05 node1 kernel: [31704.810029] (php-
> fpm,30917,1):ocfs2_orphan_del:2331 ERROR: status = -2
> Jun 24 06:43:05 node1 kernel: [31704.810034] (php-
> fpm,30917,1):ocfs2_orphan_del:2362 ERROR: status = -2
> Jun 24 06:43:05 node1 kernel: [31704.810037] (php-
> fpm,30917,1):ocfs2_remove_inode:653 ERROR: status = -2
> Jun 24 06:43:05 node1 kernel: [31704.810041] (php-
> fpm,30917,1):ocfs2_wipe_inode:798 ERROR: status = -2
> Jun 24 06:43:05 node1 kernel: [31704.810044] (php-
> fpm,30917,1):ocfs2_delete_inode:1050 ERROR: status = -2
> Jun 24 06:44:27 node1 o2hbmonitor: mount debugfs at /sys/kernel/debug
> Jun 24 06:45:09 node1 kernel: [31828.939394] 
> (kworker/u8:1,25619,1):ocfs2_orphan_del:2331 ERROR: status = -2
> Jun 24 06:45:09 node1 kernel: [31828.939399] 
> (kworker/u8:1,25619,1):ocfs2_orphan_del:2362 ERROR: status = -2
> Jun 24 06:45:09 node1 kernel: [31828.939402] 
> (kworker/u8:1,25619,1):ocfs2_remove_inode:653 ERROR: status = -2
> Jun 24 06:45:09 node1 kernel: [31828.939406] 
> (kworker/u8:1,25619,1):ocfs2_wipe_inode:798 ERROR: status = -2
> Jun 24 06:45:09 node1 kernel: [31828.939409] 
> (kworker/u8:1,25619,1):ocfs2_delete_inode:1050 ERROR: status = -2
> Jun 24 06:45:09 node1 kernel: [31828.943074] 
> (kworker/u8:1,25619,1):ocfs2_orphan_del:2331 ERROR: status = -2
> Jun 24 06:45:09 node1 kernel: [31828.943078] 
> (kworker/u8:1,25619,1):ocfs2_orphan_del:2362 ERROR: status = -2
> Jun 24 06:45:09 node1 kernel: [31828.943081] 
> (kworker/u8:1,25619,1):ocfs2_remove_inode:653 ERROR: status = -2
> Jun 24 06:45:09 node1 kernel: [31828.943084] 
> (kworker/u8:1,25619,1):ocfs2_wipe_inode:798 ERROR: status = -2
> Jun 24 06:45:09 node1 kernel: [31828.943087] 
> (kworker/u8:1,25619,1):ocfs2_delete_inode:1050 ERROR: status = -2
> Jun 24 06:45:09 node1 kernel: [31828.951077]  
> (kworker/u8:1,25619,1):ocfs2_orphan_del:2331 ERROR: status = -2
> Jun 24 06:45:09 node1 kernel: [31828.951081] 
> (kworker/u8:1,25619,1):ocfs2_orphan_del:2362 ERROR: status = -2
> Jun 24 06:45:09 node1 kernel: [31828.951083] 
> (kworker/u8:1,25619,1):ocfs2_remove_inode:653 ERROR: status = -2
> Jun 24 06:45:09 node1 kernel: [31828.951087] 
> (kworker/u8:1,25619,1):ocfs2_wipe_inode:798 ERROR: status = -2
> Jun 24 06:45:09 node1 kernel: [31828.951089] 
> (kworker/u8:1,25619,1):ocfs2_delete_inode:1050 ERROR: status = -2
> 
> and so on. FSCK (ocfs2_tools 1.8.4) every time found and fix lots of "orphaned 
> cluster" errors but after mount this starts again.
> 
> in namei.c I found that this starts from ocfs2_find_entry  - so there is some 
> filesystem errors leaved even after fsck 
> 
> WBR,
> Dmitry V.
> 
> 
> 
> 
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
> 
> 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-06-25  1:28 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-06-24  7:15 [Ocfs2-devel] OCFS2 errors in log EVEN just after FSCK vde at ykoctpa.ru
2015-06-25  1:28 ` Joseph Qi

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.