On Tue, Jan 17, 2012 at 5:08 AM, Karoly Horvath <rhswdev@xxxxxxxxx> wrote:
> Hi,
>
> I did this test on the new ceph 0.40-1oneiric package.
>
> I removed the power cord from beta.
>
> alpha became the new active MDS
> 2012-01-17 12:32:36.817012 mds e494: 1/1/1 up {0=alpha=up:active}
> but I still couldn't access the ceph fs, so I tried lazy force umount
> as you suggested:
> umount -lf ceph_mnt_point/
> but it never returned.
>
> I attached the logs.
To diagnose a problem like that we're going to need the client logs.
If nothing else there's probably some relevant output in dmesg? Also,
what kernel version?
Everything I checked looked good for the rest of the system; did you
check if new clients could do things appropriately?
-Greg
> (note: I removed a huge chunk of the alpha mds log covering approx 1 minute)
>
> --
> Karoly Horvath
>
>
> On Wed, Dec 21, 2011 at 4:13 PM, Gregory Farnum
> <gregory.farnum@xxxxxxxxxxxxx> wrote:
>> [Re-added list]
>>
>> On Wed, Dec 21, 2011 at 4:33 AM, Karoly Horvath <rhswdev@xxxxxxxxx> wrote:
>>> On Wed, Dec 21, 2011 at 12:03 AM, Gregory Farnum
>>>> It looks like maybe you got it turned on in the mon section rather
>>>> than the mds or global sections. :)
>>>
>>> right
>>>
>>>> However, as I look at these a little more it generally looks good,
>>>> even in trial 3. The only alarming thing that's present is a note that
>>>> two of your clients failed to reconnect to the MDS in time and were
>>>> cut off. Did you try establishing a new connection to the cluster and
>>>> seeing if that worked? It's possible there's a client bug, or that
>>>> there was some sort of network error that interfered with them.
>>>> -Greg
>>>
>>> By client I assume you mean the kernel driver.. the FS is freezed, so
>>> I cannot unmount (cannot even `shutdown`).. how can I force the client
>>> to reconnect?
>>
>> Try a lazy force unmount:
>> umount -lf ceph_mnt_point/
>> And then mount again.
--
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
