I see a lot of this:
2011-12-06 19:42:50.401143 7fc8b1850700 mds.0.locker i want to change
file_max, but lock won't allow it (yet)
2011-12-06 19:42:50.401168 7fc8b1850700 mds.0.locker file_excl (ifile
sync) on [inode 10000000cda [2,head] /noah.bin auth v1600 s=0 n(v0
1=1+0) (iversion lock) cr={6143=0-67108864@1}
caps={6139=-/pFscr@2,6143=pAsLsXsFc/pFscr@4},l=6143 | c
aps dirty 0x1f87c80]
Unfortunately I'm having trouble thinking straight so dealing with it
will have to wait until morning, but it shouldn't be too hard to track
down what's happening.
On Tue, Dec 6, 2011 at 9:07 PM, Noah Watkins <jayhawk@xxxxxxxxxxx> wrote:
> On 12/6/11 8:49 PM, Gregory Farnum wrote:
>>
>> The client is waiting for the MDS to give it permission to make the
>> file larger. I think this data comes back in a caps message, but it
>> probably got stuck on the MDS for some reason. Try grepping through
>> the MDS and client logs for max_size and see if there's something
>> obvious (or send it our way).
>
>
> Logs are here:
>
> http://piha.soe.ucsc.edu/cephlogs/max_size/
>
> -Noah
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
