[Ocfs2-devel] add error check for ocfs2_read_locked_inode() call

[Ocfs2-devel] add error check for ocfs2_read_locked_inode() call

[Oleg Gawriloff]

After upgrading from 2.6.28.10 to 2.6.29.3 I've saw following new errors 
in kernel log:
May 12 14:46:41 falcon-cl5
May 12 14:46:41 falcon-cl5 (6757,7):ocfs2_read_locked_inode:466 ERROR: 
status = -22

Only one node is mounted volumes in cluster:
/dev/sde on /home/apache/users/D1 type ocfs2 
(rw,_netdev,noatime,heartbeat=local)
/dev/sdd on /home/apache/users/D2 type ocfs2 
(rw,_netdev,noatime,heartbeat=local)
/dev/sdc on /home/apache/users/D3 type ocfs2 
(rw,_netdev,noatime,heartbeat=local)
The error appears multiple times per second and only numbers is different.
May 12 14:47:09 falcon-cl5 (6755,6):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 12 14:47:09 falcon-cl5
May 12 14:47:09 falcon-cl5 (6755,2):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 12 14:47:09 falcon-cl5
May 12 14:47:09 falcon-cl5 (6755,1):ocfs2_read_locked_inode:466 ERROR: 
status = -22

What does it means, any suggestions?

[Ocfs2-devel] add error check for ocfs2_read_locked_inode() call

[Sunil Mushran]

Oleg Gawriloff wrote:
> After upgrading from 2.6.28.10 to 2.6.29.3 I've saw following new errors 
> in kernel log:
> May 12 14:46:41 falcon-cl5
> May 12 14:46:41 falcon-cl5 (6757,7):ocfs2_read_locked_inode:466 ERROR: 
> status = -22
>
> Only one node is mounted volumes in cluster:
> /dev/sde on /home/apache/users/D1 type ocfs2 
> (rw,_netdev,noatime,heartbeat=local)
> /dev/sdd on /home/apache/users/D2 type ocfs2 
> (rw,_netdev,noatime,heartbeat=local)
> /dev/sdc on /home/apache/users/D3 type ocfs2 
> (rw,_netdev,noatime,heartbeat=local)
> The error appears multiple times per second and only numbers is different.
> May 12 14:47:09 falcon-cl5 (6755,6):ocfs2_read_locked_inode:466 ERROR: 
> status = -22
> May 12 14:47:09 falcon-cl5
> May 12 14:47:09 falcon-cl5 (6755,2):ocfs2_read_locked_inode:466 ERROR: 
> status = -22
> May 12 14:47:09 falcon-cl5
> May 12 14:47:09 falcon-cl5 (6755,1):ocfs2_read_locked_inode:466 ERROR: 
> status = -22
>
> What does it means, any suggestions?

I went thru the relevant code in 2.6.29-3. There has to be another
message. That is, other than the one listed.

http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.29.y.git;a=blob;f=fs/ocfs2/inode.c;h=229e707bc050629c0ad372b14c75194bf4b97f3d;hb=e18346d68f807c62bb8e5de0f809d3a1a2f093de

Did you modify the code? Apply some patches?

[Ocfs2-devel] add error check for ocfs2_read_locked_inode() call

[Oleg Gawriloff]

Sunil Mushran ?????:
> I went thru the relevant code in 2.6.29-3. There has to be another
> message. That is, other than the one listed.
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.29.y.git;a=blob;f=fs/ocfs2/inode.c;h=229e707bc050629c0ad372b14c75194bf4b97f3d;hb=e18346d68f807c62bb8e5de0f809d3a1a2f093de 
> Did you modify the code? Apply some patches?
Nope. Standard vanilla-sources 2.6.29.3 on gentoo. No patches/modifies.
barzog at falcon-cl3 ~ $ ls -l /usr/src/linux/fs/ocfs2/inode.c
-rw-r--r-- 1 root root 37345 ??? 24 01:12 /usr/src/linux/fs/ocfs2/inode.c
If needed I can give you access to this server.

[Ocfs2-devel] add error check for ocfs2_read_locked_inode() call

[Oleg Gawriloff]

Sunil Mushran ?????:
> Oleg Gawriloff wrote:
>> After upgrading from 2.6.28.10 to 2.6.29.3 I've saw following new 
>> errors in kernel log:
>> May 12 14:46:41 falcon-cl5
>> May 12 14:46:41 falcon-cl5 (6757,7):ocfs2_read_locked_inode:466 ERROR: 
>> status = -22
> Did you modify the code? Apply some patches?
According to string number in kernel log I've see thats this block is in 
inode.c string 466:
         if (status < 0) {
                 mlog_errno(status);
                 goto bail;
         }
in ocfs2_read_locked_inode. How can we further investigate this issue?

btw one of 3 mounted ocfs2 filesystems goes to ro mode without obvious 
reason.

[Ocfs2-devel] add error check for ocfs2_read_locked_inode() call

[Joel Becker]

On Wed, May 13, 2009 at 08:09:08PM +0300, Oleg Gawriloff wrote:
> Sunil Mushran ?????:
> > Oleg Gawriloff wrote:
> >> After upgrading from 2.6.28.10 to 2.6.29.3 I've saw following new 
> >> errors in kernel log:
> >> May 12 14:46:41 falcon-cl5
> >> May 12 14:46:41 falcon-cl5 (6757,7):ocfs2_read_locked_inode:466 ERROR: 
> >> status = -22
> > Did you modify the code? Apply some patches?
> According to string number in kernel log I've see thats this block is in 
> inode.c string 466:
>          if (status < 0) {
>                  mlog_errno(status);
>                  goto bail;
>          }
> in ocfs2_read_locked_inode. How can we further investigate this issue?
> 
> btw one of 3 mounted ocfs2 filesystems goes to ro mode without obvious 
> reason.

	There's no other error messages?  Can you give us a larger
snippet of the log?

Joel
-- 

Life's Little Instruction Book #15

	"Own a great stereo system."

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127

[Ocfs2-devel] add error check for ocfs2_read_locked_inode() call

[Oleg Gawriloff]

Joel Becker ?????:
> 	There's no other error messages?  Can you give us a larger
> snippet of the log?
Here:
May 13 19:51:18 falcon-cl5
May 13 19:51:18 falcon-cl5 (8824,2):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 13 19:51:18 falcon-cl5
May 13 19:51:18 falcon-cl5 (8824,2):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 13 19:51:18 falcon-cl5
May 13 19:51:18 falcon-cl5 (8824,6):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 13 19:51:18 falcon-cl5
May 13 19:51:18 falcon-cl5 (8824,1):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 13 19:51:18 falcon-cl5
till 21:15 all the same:
May 13 21:15:35 falcon-cl5 (9246,6):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 13 21:15:35 falcon-cl5
May 13 21:15:35 falcon-cl5 (9246,4):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 13 21:15:35 falcon-cl5
May 13 21:15:35 falcon-cl5 (9246,5):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 13 21:15:35 falcon-cl5
May 13 21:15:35 falcon-cl5 (9246,7):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 13 21:15:35 falcon-cl5
May 13 21:15:35 falcon-cl5 (9246,0):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 13 21:15:35 falcon-cl5
May 13 21:15:35 falcon-cl5 (9246,2):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 13 21:15:35 falcon-cl5

Then I rebooted first node:
May 13 21:15:35 falcon-cl5 (9246,1):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 13 21:30:58 falcon-cl5 o2net: no longer connected to node falcon-cl1 
(num 0) at 172.16.2.228:7777
May 13 21:31:00 falcon-cl5 (5819,6):dlm_send_proxy_ast_msg:458 ERROR: 
status = -107
May 13 21:31:00 falcon-cl5 (5819,6):dlm_flush_asts:584 ERROR: status = -107
May 13 21:31:00 falcon-cl5 (5819,6):dlm_send_proxy_ast_msg:458 ERROR: 
status = -107
May 13 21:31:00 falcon-cl5 (5819,6):dlm_flush_asts:584 ERROR: status = -107
May 13 21:31:01 falcon-cl5 (5819,6):dlm_send_proxy_ast_msg:458 ERROR: 
status = -107
May 13 21:31:01 falcon-cl5 (5819,6):dlm_flush_asts:584 ERROR: status = -107
May 13 21:31:01 falcon-cl5 (5819,6):dlm_send_proxy_ast_msg:458 ERROR: 
status = -107
May 13 21:31:01 falcon-cl5 (5819,6):dlm_flush_asts:584 ERROR: status = -107
May 13 21:31:03 falcon-cl5 (9319,6):dlm_do_master_request:1352 ERROR: 
link to 0 went down!
May 13 21:31:03 falcon-cl5 (9319,6):dlm_get_lock_resource:929 ERROR: 
status = -107
some of same lines skipped:
May 13 21:31:03 falcon-cl5 (9319,6):dlm_do_master_request:1352 ERROR: 
link to 0 went down!
May 13 21:31:03 falcon-cl5 (9319,6):dlm_get_lock_resource:929 ERROR: 
status = -107
May 13 21:31:04 falcon-cl5 (344,6):dlm_send_remote_unlock_request:359 
ERROR: status = -107
May 13 21:31:04 falcon-cl5 (344,6):dlm_send_remote_unlock_request:359 
ERROR: status = -107
May 13 21:31:04 falcon-cl5 (344,6):dlm_send_remote_unlock_request:359 
ERROR: status = -107

Then first node starts:
May 13 21:33:38 falcon-cl5 (5762,6):o2net_connect_expired:1659 ERROR: no 
connection established with node 0 after 160.0 seconds, giving up and 
returning errors.
May 13 21:33:41 falcon-cl5 (344,6):dlm_send_remote_unlock_request:359 
ERROR: status = -107
May 13 21:33:41 falcon-cl5 (344,6):dlm_send_remote_unlock_request:359 
ERROR: status = -107
May 13 21:33:41 falcon-cl5 (344,6):dlm_send_remote_unlock_request:359 
ERROR: status = -107
May 13 21:33:49 falcon-cl5 (5819,3):dlm_drop_lockres_ref:2229 ERROR: 
status = -107
May 13 21:33:49 falcon-cl5 (5819,3):dlm_purge_lockres:190 ERROR: status 
= -107
May 13 21:33:49 falcon-cl5 (5819,3):dlm_drop_lockres_ref:2229 ERROR: 
status = -107
May 13 21:33:49 falcon-cl5 (5819,3):dlm_purge_lockres:190 ERROR: status 
= -107
May 13 21:33:49 falcon-cl5 (5819,3):dlm_drop_lockres_ref:2229 ERROR: 
status = -107
May 13 21:33:49 falcon-cl5 (5819,3):dlm_purge_lockres:190 ERROR: status 
= -107
May 13 21:35:31 falcon-cl5 (5837,7):o2dlm_eviction_cb:258 o2dlm has 
evicted node 0 from group 558A175E1CC94570940D9BEFCAE48B8E
May 13 21:35:31 falcon-cl5 (5837,7):o2dlm_eviction_cb:258 o2dlm has 
evicted node 0 from group 0AF561B8464D47C78DCC544ADC5273A5
May 13 21:35:31 falcon-cl5 (9367,2):dlm_get_lock_resource:856 
558A175E1CC94570940D9BEFCAE48B8E:M000000000000000000002682719dd6: at 
least one node (0) to recover before lock mastery can begin
May 13 21:35:31 falcon-cl5 (5837,0):o2dlm_eviction_cb:258 o2dlm has 
evicted node 0 from group A474A15478334D959A30A50ED6530ABE
May 13 21:35:31 falcon-cl5 (9368,7):dlm_get_lock_resource:856 
0AF561B8464D47C78DCC544ADC5273A5:M00000000000000000000a65cc0060a: at 
least one node (0) to recover before lock mastery can begin
May 13 21:35:31 falcon-cl5 (9369,0):dlm_get_lock_resource:856 
A474A15478334D959A30A50ED6530ABE:M00000000000000000000260046dbbf: at 
least one node (0) to recover before lock mastery can begin
May 13 21:35:32 falcon-cl5 (9367,2):dlm_get_lock_resource:910 
558A175E1CC94570940D9BEFCAE48B8E:M000000000000000000002682719dd6: at 
least one node (0) to recover before lock mastery can begin
May 13 21:35:32 falcon-cl5 (9368,7):dlm_get_lock_resource:910 
0AF561B8464D47C78DCC544ADC5273A5:M00000000000000000000a65cc0060a: at 
least one node (0) to recover before lock mastery can begin
May 13 21:35:32 falcon-cl5 (9369,0):dlm_get_lock_resource:910 
A474A15478334D959A30A50ED6530ABE:M00000000000000000000260046dbbf: at 
least one node (0) to recover before lock mastery can begin
May 13 21:35:34 falcon-cl5 (6309,6):dlm_restart_lock_mastery:1235 ERROR: 
node down! 0
May 13 21:35:34 falcon-cl5 (6309,6):dlm_wait_for_lock_mastery:1052 
ERROR: status = -11
May 13 21:35:34 falcon-cl5 (5840,3):dlm_get_lock_resource:856 
A474A15478334D959A30A50ED6530ABE:$RECOVERY: at least one node (0) to 
recover before lock mastery can begin
May 13 21:35:34 falcon-cl5 (5840,3):dlm_get_lock_resource:890 
A474A15478334D959A30A50ED6530ABE: recovery map is not empty, but must 
master $RECOVERY lock now
May 13 21:35:34 falcon-cl5 (5840,3):dlm_do_recovery:524 (5840) Node 4 is 
the Recovery Master for the Dead Node 0 for Domain 
A474A15478334D959A30A50ED6530ABE
May 13 21:35:34 falcon-cl5 (5830,7):dlm_get_lock_resource:856 
0AF561B8464D47C78DCC544ADC5273A5:$RECOVERY: at least one node (0) to 
recover before lock mastery can begin
May 13 21:35:34 falcon-cl5 (5830,7):dlm_get_lock_resource:890 
0AF561B8464D47C78DCC544ADC5273A5: recovery map is not empty, but must 
master $RECOVERY lock now
May 13 21:35:34 falcon-cl5 (5830,7):dlm_do_recovery:524 (5830) Node 4 is 
the Recovery Master for the Dead Node 0 for Domain 
0AF561B8464D47C78DCC544ADC5273A5
May 13 21:35:35 falcon-cl5 (6309,6):dlm_get_lock_resource:910 
558A175E1CC94570940D9BEFCAE48B8E:N0000000000a7b250: at least one node 
(0) to recover before lock mastery can begin
May 13 21:35:35 falcon-cl5 (5820,2):dlm_get_lock_resource:856 
558A175E1CC94570940D9BEFCAE48B8E:$RECOVERY: at least one node (0) to 
recover before lock mastery can begin
May 13 21:35:35 falcon-cl5 (5820,2):dlm_get_lock_resource:890 
558A175E1CC94570940D9BEFCAE48B8E: recovery map is not empty, but must 
master $RECOVERY lock now
May 13 21:35:35 falcon-cl5 (5820,2):dlm_do_recovery:524 (5820) Node 4 is 
the Recovery Master for the Dead Node 0 for Domain 
558A175E1CC94570940D9BEFCAE48B8E
May 13 21:35:43 falcon-cl5 (9367,1):ocfs2_replay_journal:1470 Recovering 
node 0 from slot 2 on device (8,64)
May 13 21:35:43 falcon-cl5 (9368,0):ocfs2_replay_journal:1470 Recovering 
node 0 from slot 2 on device (8,48)
May 13 21:35:43 falcon-cl5 (9369,3):ocfs2_replay_journal:1470 Recovering 
node 0 from slot 2 on device (8,32)
May 13 21:35:54 falcon-cl5 kjournald2 starting: pid 9370, dev sde:38, 
commit interval 5 seconds
May 13 21:35:54 falcon-cl5 kjournald2 starting: pid 9371, dev sdd:166, 
commit interval 5 seconds
May 13 21:35:54 falcon-cl5 (9367,3):ocfs2_begin_quota_recovery:374 
Beginning quota recovery in slot 2
May 13 21:35:54 falcon-cl5 (9368,2):ocfs2_begin_quota_recovery:374 
Beginning quota recovery in slot 2
May 13 21:35:54 falcon-cl5 kjournald2 starting: pid 9372, dev sdc:38, 
commit interval 5 seconds
May 13 21:35:55 falcon-cl5 (9369,5):ocfs2_begin_quota_recovery:374 
Beginning quota recovery in slot 2
May 13 21:35:55 falcon-cl5 (3127,2):ocfs2_finish_quota_recovery:564 
Finishing quota recovery in slot 2
May 13 21:35:56 falcon-cl5 (3127,4):ocfs2_finish_quota_recovery:564 
Finishing quota recovery in slot 2
May 13 21:35:56 falcon-cl5 (3127,4):ocfs2_finish_quota_recovery:564 
Finishing quota recovery in slot 2
May 13 21:35:57 falcon-cl5 o2net: connected to node falcon-cl1 (num 0) 
at 172.16.2.228:7777
May 13 21:36:01 falcon-cl5 ocfs2_dlm: Node 0 joins domain 
558A175E1CC94570940D9BEFCAE48B8E
May 13 21:36:01 falcon-cl5 ocfs2_dlm: Nodes in domain 
("558A175E1CC94570940D9BEFCAE48B8E"): 0 1 4
May 13 21:36:05 falcon-cl5 ocfs2_dlm: Node 0 joins domain 
0AF561B8464D47C78DCC544ADC5273A5
May 13 21:36:05 falcon-cl5 ocfs2_dlm: Nodes in domain 
("0AF561B8464D47C78DCC544ADC5273A5"): 0 1 4
May 13 21:36:10 falcon-cl5 ocfs2_dlm: Node 0 joins domain 
A474A15478334D959A30A50ED6530ABE
May 13 21:36:10 falcon-cl5 ocfs2_dlm: Nodes in domain 
("A474A15478334D959A30A50ED6530ABE"): 0 1 4
May 13 21:38:54 falcon-cl5

and all the same.
May 13 21:38:54 falcon-cl5 (9337,2):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 13 21:38:54 falcon-cl5
May 13 21:38:54 falcon-cl5 (9337,7):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 13 21:38:54 falcon-cl5
May 13 21:38:54 falcon-cl5 (9337,5):ocfs2_read_locked_inode:466 ERROR: 
status = -22
May 13 21:38:54 falcon-cl5

[Ocfs2-devel] add error check for ocfs2_read_locked_inode() call

[Joel Becker]

On Wed, May 13, 2009 at 09:44:57PM +0300, Oleg Gawriloff wrote:
> Joel Becker ?????:
> > 	There's no other error messages?  Can you give us a larger
> > snippet of the log?
> Here:
> May 13 19:51:18 falcon-cl5
> May 13 19:51:18 falcon-cl5 (8824,2):ocfs2_read_locked_inode:466 ERROR: 
> status = -22

	This is really weird.  Like Sunil, I looked at the code.  And
every place that can set status to -EINVAL (-22) has its own ERROR
message.  So you should be seeing those.

Joel

-- 

"I always thought the hardest questions were those I could not answer.
 Now I know they are the ones I can never ask."
			- Charlie Watkins

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127

[Ocfs2-devel] add error check for ocfs2_read_locked_inode() call

[Sunil Mushran]

Joel Becker wrote:
> On Wed, May 13, 2009 at 09:44:57PM +0300, Oleg Gawriloff wrote:
>> Joel Becker ?????:
>>> 	There's no other error messages?  Can you give us a larger
>>> snippet of the log?
>> Here:
>> May 13 19:51:18 falcon-cl5
>> May 13 19:51:18 falcon-cl5 (8824,2):ocfs2_read_locked_inode:466 ERROR: 
>> status = -22
>
> 	This is really weird.  Like Sunil, I looked at the code.  And
> every place that can set status to -EINVAL (-22) has its own ERROR
> message.  So you should be seeing those.
>
> Joel

Exactly. Also, this could be related to that volume going read-only.
But if so, you will atleast see the following message:

        printk(KERN_CRIT "File system is now read-only due to the 
potential "
               "of on-disk corruption. Please run fsck.ocfs2 once the file "
               "system is unmounted.\n");

If the code is the same, then it could be that the difference is in the 
build.
But what, how, I cannot say.

BTW, maybe a good idea to fsck your volumes.

Sunil

[Ocfs2-devel] add error check for ocfs2_read_locked_inode() call

[Sunil Mushran]

Oleg Gawriloff wrote:
> May 13 21:35:35 falcon-cl5 (5820,2):dlm_do_recovery:524 (5820) Node 4 
> is the Recovery Master for the Dead Node 0 for Domain 
> 558A175E1CC94570940D9BEFCAE48B8E
> May 13 21:35:43 falcon-cl5 (9367,1):ocfs2_replay_journal:1470 
> Recovering node 0 from slot 2 on device (8,64)
> May 13 21:35:43 falcon-cl5 (9368,0):ocfs2_replay_journal:1470 
> Recovering node 0 from slot 2 on device (8,48)
> May 13 21:35:43 falcon-cl5 (9369,3):ocfs2_replay_journal:1470 
> Recovering node 0 from slot 2 on device (8,32)
> May 13 21:35:54 falcon-cl5 kjournald2 starting: pid 9370, dev sde:38, 
> commit interval 5 seconds
> May 13 21:35:54 falcon-cl5 kjournald2 starting: pid 9371, dev sdd:166, 
> commit interval 5 seconds
> May 13 21:35:54 falcon-cl5 (9367,3):ocfs2_begin_quota_recovery:374 
> Beginning quota recovery in slot 2
> May 13 21:35:54 falcon-cl5 (9368,2):ocfs2_begin_quota_recovery:374 
> Beginning quota recovery in slot 2
> May 13 21:35:54 falcon-cl5 kjournald2 starting: pid 9372, dev sdc:38, 
> commit interval 5 seconds
> May 13 21:35:55 falcon-cl5 (9369,5):ocfs2_begin_quota_recovery:374 
> Beginning quota recovery in slot 2
> May 13 21:35:55 falcon-cl5 (3127,2):ocfs2_finish_quota_recovery:564 
> Finishing quota recovery in slot 2
> May 13 21:35:56 falcon-cl5 (3127,4):ocfs2_finish_quota_recovery:564 
> Finishing quota recovery in slot 2
> May 13 21:35:56 falcon-cl5 (3127,4):ocfs2_finish_quota_recovery:564 
> Finishing quota recovery in slot 2
> May 13 21:35:57 falcon-cl5 o2net: connected to node falcon-cl1 (num 0) 
> at 172.16.2.228:7777
> May 13 21:36:01 falcon-cl5 ocfs2_dlm: Node 0 joins domain 
> 558A175E1CC94570940D9BEFCAE48B8E
> May 13 21:36:01 falcon-cl5 ocfs2_dlm: Nodes in domain 
> ("558A175E1CC94570940D9BEFCAE48B8E"): 0 1 4
> May 13 21:36:05 falcon-cl5 ocfs2_dlm: Node 0 joins domain 
> 0AF561B8464D47C78DCC544ADC5273A5
> May 13 21:36:05 falcon-cl5 ocfs2_dlm: Nodes in domain 
> ("0AF561B8464D47C78DCC544ADC5273A5"): 0 1 4
> May 13 21:36:10 falcon-cl5 ocfs2_dlm: Node 0 joins domain 
> A474A15478334D959A30A50ED6530ABE
> May 13 21:36:10 falcon-cl5 ocfs2_dlm: Nodes in domain 
> ("A474A15478334D959A30A50ED6530ABE"): 0 1 4
> May 13 21:38:54 falcon-cl5

How did you enable quotas? While the fs has support for it, the tools don't.
Meaning users cannot enable it using the tools as-is.

[Ocfs2-devel] add error check for ocfs2_read_locked_inode() call

[Joel Becker]

On Wed, May 13, 2009 at 12:12:01PM -0700, Sunil Mushran wrote:
> Oleg Gawriloff wrote:
> > May 13 21:35:55 falcon-cl5 (9369,5):ocfs2_begin_quota_recovery:374 
> > Beginning quota recovery in slot 2
> > May 13 21:35:55 falcon-cl5 (3127,2):ocfs2_finish_quota_recovery:564 
> > Finishing quota recovery in slot 2
> > May 13 21:35:56 falcon-cl5 (3127,4):ocfs2_finish_quota_recovery:564 
> > Finishing quota recovery in slot 2
> > May 13 21:35:56 falcon-cl5 (3127,4):ocfs2_finish_quota_recovery:564 
> > Finishing quota recovery in slot 2
> > May 13 21:35:57 falcon-cl5 o2net: connected to node falcon-cl1 (num 0) 
> > at 172.16.2.228:7777
> How did you enable quotas? While the fs has support for it, the tools don't.
> Meaning users cannot enable it using the tools as-is.

	I think the message is always there regardless.

Joel

-- 

"Here's a nickle -- get yourself a better X server."
	- Keith Packard

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127