* problems with xattr in 2.6.28 and 2.6.27
@ 2009-01-08 10:04 Oliver Neukum
2009-01-09 3:35 ` Jeff Mahoney
0 siblings, 1 reply; 3+ messages in thread
From: Oliver Neukum @ 2009-01-08 10:04 UTC (permalink / raw)
To: Jeff Mahoney; +Cc: reiserfs-devel
Hi,
I am getting entries like this in syslog, but reiserfsck finds no errors
in the filesystem.
Regards
Oliver
2.6.28:
Jan 8 08:55:14 vanamonde kernel: REISERFS warning (device sda7): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) assoc
iated with [266558 266621 0x0 SD]
Jan 8 08:55:14 vanamonde kernel: REISERFS warning (device sda7): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) assoc
iated with [266558 266631 0x0 SD]
Jan 8 08:55:14 vanamonde kernel: REISERFS warning (device sda7): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) assoc
iated with [266558 266669 0x0 SD]
Jan 8 08:55:15 vanamonde kernel: REISERFS warning (device sda7): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) assoc
iated with [266558 266691 0x0 SD]
Jan 8 08:55:16 vanamonde kernel: REISERFS warning (device sda7): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) assoc
iated with [266558 266621 0x0 SD]
Jan 8 08:55:16 vanamonde kernel: REISERFS warning (device sda7): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) assoc
iated with [266558 266631 0x0 SD]
Jan 8 08:55:16 vanamonde kernel: REISERFS warning (device sda7): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) assoc
iated with [266558 266669 0x0 SD]
2.6.27:
Jan 7 16:33:06 vanamonde kernel: ReiserFS: sda7: warning: Invalid hash for xattr (user.Beagle) associated with [959459378 3158320 0x0 SD]
Jan 7 16:33:06 vanamonde kernel: ReiserFS: sda7: warning: Invalid hash for xattr (user.Beagle) associated with [959459378 3158320 0x0 SD]
Jan 7 16:33:06 vanamonde kernel: ReiserFS: sda7: warning: Invalid hash for xattr (user.Beagle) associated with [959459378 3158320 0x0 SD]
Jan 7 16:33:06 vanamonde kernel: ReiserFS: sda7: warning: Invalid hash for xattr (user.Beagle) associated with [959459378 3158320 0x0 SD]
Jan 7 16:33:06 vanamonde kernel: ReiserFS: sda7: warning: Invalid hash for xattr (user.Beagle) associated with [959459378 3158320 0x0 SD]
Jan 7 16:33:07 vanamonde kernel: ReiserFS: sda7: warning: Invalid hash for xattr (user.Beagle) associated with [959459378 892350768 892548608(49) DIR]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: problems with xattr in 2.6.28 and 2.6.27
2009-01-08 10:04 problems with xattr in 2.6.28 and 2.6.27 Oliver Neukum
@ 2009-01-09 3:35 ` Jeff Mahoney
2009-01-09 22:50 ` Oliver Neukum
0 siblings, 1 reply; 3+ messages in thread
From: Jeff Mahoney @ 2009-01-09 3:35 UTC (permalink / raw)
To: Oliver Neukum; +Cc: reiserfs-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Oliver Neukum wrote:
> Hi,
>
> I am getting entries like this in syslog, but reiserfsck finds no errors
> in the filesystem.
Yeah, reiserfsck doesn't check them. If you run into these once in a
while, then setfattr -b is the answer. If you're seeing them en masse,
something is wonky.
I saw a report on b.n.c indicating that someone ran into these while
running a vanilla kernel, but the suse kernel doesn't exhibit the
problem. This isn't really surprising since the suse kernel contains the
"latest" reiser3 development. I know. I need to push it upstream.
- -Jeff
> Regards
> Oliver
> 2.6.28:
>
> Jan 8 08:55:14 vanamonde kernel: REISERFS warning (device sda7): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) assoc
> iated with [266558 266621 0x0 SD]
> Jan 8 08:55:14 vanamonde kernel: REISERFS warning (device sda7): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) assoc
> iated with [266558 266631 0x0 SD]
> Jan 8 08:55:14 vanamonde kernel: REISERFS warning (device sda7): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) assoc
> iated with [266558 266669 0x0 SD]
> Jan 8 08:55:15 vanamonde kernel: REISERFS warning (device sda7): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) assoc
> iated with [266558 266691 0x0 SD]
> Jan 8 08:55:16 vanamonde kernel: REISERFS warning (device sda7): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) assoc
> iated with [266558 266621 0x0 SD]
> Jan 8 08:55:16 vanamonde kernel: REISERFS warning (device sda7): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) assoc
> iated with [266558 266631 0x0 SD]
> Jan 8 08:55:16 vanamonde kernel: REISERFS warning (device sda7): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) assoc
> iated with [266558 266669 0x0 SD]
>
> 2.6.27:
>
> Jan 7 16:33:06 vanamonde kernel: ReiserFS: sda7: warning: Invalid hash for xattr (user.Beagle) associated with [959459378 3158320 0x0 SD]
> Jan 7 16:33:06 vanamonde kernel: ReiserFS: sda7: warning: Invalid hash for xattr (user.Beagle) associated with [959459378 3158320 0x0 SD]
> Jan 7 16:33:06 vanamonde kernel: ReiserFS: sda7: warning: Invalid hash for xattr (user.Beagle) associated with [959459378 3158320 0x0 SD]
> Jan 7 16:33:06 vanamonde kernel: ReiserFS: sda7: warning: Invalid hash for xattr (user.Beagle) associated with [959459378 3158320 0x0 SD]
> Jan 7 16:33:06 vanamonde kernel: ReiserFS: sda7: warning: Invalid hash for xattr (user.Beagle) associated with [959459378 3158320 0x0 SD]
> Jan 7 16:33:07 vanamonde kernel: ReiserFS: sda7: warning: Invalid hash for xattr (user.Beagle) associated with [959459378 892350768 892548608(49) DIR]
> --
> 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
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAklmxfQACgkQLPWxlyuTD7K53gCfVN+4+xbPrxGyZ7tcQR/OKpDh
YlsAnRoW8vqx2LjZBJtMXcCALzoBe5RP
=65z7
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: problems with xattr in 2.6.28 and 2.6.27
2009-01-09 3:35 ` Jeff Mahoney
@ 2009-01-09 22:50 ` Oliver Neukum
0 siblings, 0 replies; 3+ messages in thread
From: Oliver Neukum @ 2009-01-09 22:50 UTC (permalink / raw)
To: Jeff Mahoney; +Cc: reiserfs-devel
Am Friday 09 January 2009 04:35:16 schrieb Jeff Mahoney:
> Oliver Neukum wrote:
> > Hi,
> >
> > I am getting entries like this in syslog, but reiserfsck finds no errors
> > in the filesystem.
>
> Yeah, reiserfsck doesn't check them. If you run into these once in a
Strictly speaking, isn't it a bit fishy to not test something in fsck the
kernel has a run time test for?
> while, then setfattr -b is the answer. If you're seeing them en masse,
> something is wonky.
>
> I saw a report on b.n.c indicating that someone ran into these while
> running a vanilla kernel, but the suse kernel doesn't exhibit the
> problem. This isn't really surprising since the suse kernel contains the
> "latest" reiser3 development. I know. I need to push it upstream.
Indeed. Only the vanilla kernel seems to be affected. Running with
additional debugging I get a circular dependency trace from 2.6.28.
Regards
Oliver
Jan 8 16:45:58 vanamonde kernel: =======================================================
Jan 8 16:45:58 vanamonde kernel: [ INFO: possible circular locking dependency detected ]
Jan 8 16:45:58 vanamonde kernel: 2.6.28-9-default #2
Jan 8 16:45:58 vanamonde kernel: -------------------------------------------------------
Jan 8 16:45:58 vanamonde kernel: kmail/6496 is trying to acquire lock:
Jan 8 16:45:58 vanamonde kernel: (&type->i_mutex_dir_key#5){--..}, at: [<ffffffff802bb436>] vfs_rmdir+0x98/0x115
Jan 8 16:45:58 vanamonde kernel:
Jan 8 16:45:58 vanamonde kernel: but task is already holding lock:
Jan 8 16:45:58 vanamonde kernel: (&REISERFS_SB(s)->xattr_dir_sem){----}, at: [<ffffffffa01f7823>] reiserfs_delete_xattrs+0xff/0x16b [reiserfs]
Jan 8 16:45:58 vanamonde kernel:
Jan 8 16:45:58 vanamonde kernel: which lock already depends on the new lock.
Jan 8 16:45:58 vanamonde kernel:
Jan 8 16:45:58 vanamonde kernel:
Jan 8 16:45:58 vanamonde kernel: the existing dependency chain (in reverse order) is:
Jan 8 16:45:58 vanamonde kernel:
Jan 8 16:45:58 vanamonde kernel: -> #2 (&REISERFS_SB(s)->xattr_dir_sem){----}:
Jan 8 16:45:58 vanamonde kernel: [<ffffffff8025c34f>] __lock_acquire+0x12b0/0x161a
Jan 8 16:45:58 vanamonde kernel: [<ffffffff8025c70e>] lock_acquire+0x55/0x71
Jan 8 16:45:58 vanamonde kernel: [<ffffffff8047262f>] down_read+0x40/0x4d
Jan 8 16:45:58 vanamonde kernel: [<ffffffffa01f666f>] reiserfs_check_acl+0x37/0xb6 [reiserfs]
Jan 8 16:45:58 vanamonde kernel: [<ffffffff802b9f20>] generic_permission+0x58/0x101
Jan 8 16:45:58 vanamonde kernel: [<ffffffffa01f6636>] reiserfs_permission+0x26/0x28 [reiserfs]
Jan 8 16:45:58 vanamonde kernel: [<ffffffff802ba032>] inode_permission+0x69/0x97
Jan 8 16:45:58 vanamonde kernel: [<ffffffff802bbf20>] __link_path_walk+0x134/0xde0
Jan 8 16:45:58 vanamonde kernel: [<ffffffff802bcdd2>] path_walk+0x69/0xd4
Jan 8 16:45:58 vanamonde kernel: [<ffffffff802bd06b>] do_path_lookup+0x187/0x1df
Jan 8 16:45:58 vanamonde kernel: [<ffffffff802bd181>] path_lookup_open+0x5a/0x9b
Jan 8 16:45:58 vanamonde kernel: [<ffffffff802bdd68>] do_filp_open+0xb6/0x8a2
Jan 8 16:45:58 vanamonde kernel: [<ffffffff802b0f32>] do_sys_open+0x53/0xd3
Jan 8 16:45:58 vanamonde kernel: [<ffffffff802b0fdb>] sys_open+0x1b/0x1d
Jan 8 16:45:58 vanamonde kernel: [<ffffffff8020c0db>] system_call_fastpath+0x16/0x1b
Jan 8 16:45:58 vanamonde kernel: [<ffffffffffffffff>] 0xffffffffffffffff
Jan 8 16:45:58 vanamonde kernel:
Jan 8 16:45:58 vanamonde kernel: -> #1 (&REISERFS_I(inode)->xattr_sem){----}:
Jan 8 16:45:58 vanamonde kernel: [<ffffffff8025c34f>] __lock_acquire+0x12b0/0x161a
Jan 8 16:45:58 vanamonde kernel: [<ffffffff8025c70e>] lock_acquire+0x55/0x71
Jan 8 16:45:58 vanamonde kernel: [<ffffffff8047262f>] down_read+0x40/0x4d
Jan 8 16:45:58 vanamonde kernel: [<ffffffffa01f8f50>] reiserfs_cache_default_acl+0x41/0xc8 [reiserfs]
Jan 8 16:45:58 vanamonde kernel: [<ffffffffa01da250>] reiserfs_create+0x81/0x226 [reiserfs]
Jan 8 16:45:58 vanamonde kernel: [<ffffffff802bbab4>] vfs_create+0xea/0x161
Jan 8 16:45:58 vanamonde kernel: [<ffffffff802bdf09>] do_filp_open+0x257/0x8a2
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802b0f32>] do_sys_open+0x53/0xd3
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802b0fdb>] sys_open+0x1b/0x1d
Jan 8 16:45:59 vanamonde kernel: [<ffffffff8020c0db>] system_call_fastpath+0x16/0x1b
Jan 8 16:45:59 vanamonde kernel: [<ffffffffffffffff>] 0xffffffffffffffff
Jan 8 16:45:59 vanamonde kernel:
Jan 8 16:45:59 vanamonde kernel: -> #0 (&type->i_mutex_dir_key#5){--..}:
Jan 8 16:45:59 vanamonde kernel: [<ffffffff8025c01e>] __lock_acquire+0xf7f/0x161a
Jan 8 16:45:59 vanamonde kernel: [<ffffffff8025c70e>] lock_acquire+0x55/0x71
Jan 8 16:45:59 vanamonde kernel: [<ffffffff80471bb3>] mutex_lock_nested+0x10c/0x2a9
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802bb436>] vfs_rmdir+0x98/0x115
Jan 8 16:45:59 vanamonde kernel: [<ffffffffa01f782f>] reiserfs_delete_xattrs+0x10b/0x16b [reiserfs]
Jan 8 16:45:59 vanamonde kernel: [<ffffffffa01df7df>] reiserfs_delete_inode+0x75/0x12a [reiserfs]
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802c5552>] generic_delete_inode+0xcb/0x165
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802c5603>] generic_drop_inode+0x17/0x17b
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802c471b>] iput+0x61/0x65
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802bd544>] do_unlinkat+0x107/0x15d
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802bd5ab>] sys_unlink+0x11/0x13
Jan 8 16:45:59 vanamonde kernel: [<ffffffff8020c0db>] system_call_fastpath+0x16/0x1b
Jan 8 16:45:59 vanamonde kernel: [<ffffffffffffffff>] 0xffffffffffffffff
Jan 8 16:45:59 vanamonde kernel:
Jan 8 16:45:59 vanamonde kernel: other info that might help us debug this:
Jan 8 16:45:59 vanamonde kernel:
Jan 8 16:45:59 vanamonde kernel: 1 lock held by kmail/6496:
Jan 8 16:45:59 vanamonde kernel: #0: (&REISERFS_SB(s)->xattr_dir_sem){----}, at: [<ffffffffa01f7823>] reiserfs_delete_xattrs+0xff/0x16b [reiserfs]
Jan 8 16:45:59 vanamonde kernel:
Jan 8 16:45:59 vanamonde kernel: stack backtrace:
Jan 8 16:45:59 vanamonde kernel: Pid: 6496, comm: kmail Not tainted 2.6.28-9-default #2
Jan 8 16:45:59 vanamonde kernel: Call Trace:
Jan 8 16:45:59 vanamonde kernel: [<ffffffff8025acb9>] print_circular_bug_tail+0xc5/0xd0
Jan 8 16:45:59 vanamonde kernel: [<ffffffff8025c01e>] __lock_acquire+0xf7f/0x161a
Jan 8 16:45:59 vanamonde kernel: [<ffffffff8025c70e>] lock_acquire+0x55/0x71
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802bb436>] ? vfs_rmdir+0x98/0x115
Jan 8 16:45:59 vanamonde kernel: [<ffffffff80471bb3>] mutex_lock_nested+0x10c/0x2a9
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802bb436>] ? vfs_rmdir+0x98/0x115
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802bb436>] ? vfs_rmdir+0x98/0x115
Jan 8 16:45:59 vanamonde kernel: [<ffffffff8047375c>] ? _spin_unlock_irq+0x2b/0x30
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802ba9c7>] ? may_delete+0x65/0x144
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802bb436>] vfs_rmdir+0x98/0x115
Jan 8 16:45:59 vanamonde kernel: [<ffffffffa01f782f>] reiserfs_delete_xattrs+0x10b/0x16b [reiserfs]
Jan 8 16:45:59 vanamonde kernel: [<ffffffffa01df7df>] reiserfs_delete_inode+0x75/0x12a [reiserfs]
Jan 8 16:45:59 vanamonde kernel: [<ffffffffa01df76a>] ? reiserfs_delete_inode+0x0/0x12a [reiserfs]
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802c5552>] generic_delete_inode+0xcb/0x165
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802c5603>] generic_drop_inode+0x17/0x17b
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802c471b>] iput+0x61/0x65
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802bd544>] do_unlinkat+0x107/0x15d
Jan 8 16:45:59 vanamonde kernel: [<ffffffff8020c10c>] ? sysret_check+0x27/0x62
Jan 8 16:45:59 vanamonde kernel: [<ffffffff8025a77f>] ? trace_hardirqs_on_caller+0x114/0x138
Jan 8 16:45:59 vanamonde kernel: [<ffffffff80473383>] ? trace_hardirqs_on_thunk+0x3a/0x3f
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802bcf2b>] ? do_path_lookup+0x47/0x1df
Jan 8 16:45:59 vanamonde kernel: [<ffffffff802bd5ab>] sys_unlink+0x11/0x13
Jan 8 16:45:59 vanamonde kernel: [<ffffffff8020c0db>] system_call_fastpath+0x16/0x1b
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-01-09 22:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-08 10:04 problems with xattr in 2.6.28 and 2.6.27 Oliver Neukum
2009-01-09 3:35 ` Jeff Mahoney
2009-01-09 22:50 ` Oliver Neukum
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.