bugGluster - Bugs: bug #21918, All data appears to vanish under...

 
 

bug #21918: All data appears to vanish under certain circumstances

Submitted by:  Gareth Bult <garethbult>
Submitted on:  Mon 31 Dec 2007 11:45:04 AM UTC  
 
Category: GlusterFSSeverity: 4 - Important
Priority: 5 - NormalItem Group: Improper behaviour
Status: FixedPrivacy: Public
Assigned to: Krishna Srinivas <krishnasrinivas>Originator Name: 
Open/Closed: ClosedRelease: 
Operating System: GNU/LinuxReproducibility: None

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Wed 23 Apr 2008 09:45:08 PM UTC, comment #3:

as its reported fixed by krishna, closing the bug.

Amar Tumballi <amarts>
Project Member
Wed 23 Apr 2008 11:25:49 AM UTC, comment #2:

This was fixed.

Krishna Srinivas <krishnasrinivas>
Project MemberIn charge of this item.
Sat 12 Apr 2008 02:01:50 AM UTC, comment #1:

Hi Gareth, Any update on this bug?

Krishna, Does your patch recently committed (afr_self_heal.c) handles this situation?

-amar

Amar Tumballi <amarts>
Project Member
Mon 31 Dec 2007 11:45:04 AM UTC, original submission:

(two servers, both define a "homes" volume)

Client;

volume nodea-homes
type protocol/client
option transport-type tcp/client
option remote-host nodea
option remote-subvolume homes
end-volume

volume nodeb-homes
type protocol/client
option transport-type tcp/client
option remote-host nodeb
option remote-subvolume homes
end-volume

volume homes-afr
type cluster/afr
subvolumes nodea-homes nodeb-homes ### ISSUE IS HERE! ###
option scheduler rr
end-volume

Assume system is completely up-to-date and working Ok.
Mount homes filesystem on "client".
Kill the "nodea" server.
System carries on, effectively using nodeb.

Wipe nodea's physical volume.
Restart nodea server.

All of a sudden, "client" see's an empty "homes" filesystem, although data is still in place on "B" and "A" is blank.
i.e. the client is seeing the blank "nodea" only (!)

.. at this point you check nodeb to make sure your data really is there, then you can mop up the coffee you've just spat all over your screens ..

If you crash nodeB instead, there appears to be no problem, and a self heal "find" will correct the blank volume.
Alternatively, if you reverse the subvolumes as listed above, you don't see the problem.

The issue appears to be blanking the first subvolume.

I'm thinking the order of the volumes should not be an issue, gluster should know one volume is empty / new and one contains real data and act accordingly, rather than relying on the order volumes are listed .. (???)

I'm using fuse glfs7 and gluster 1.3.8 (tla).

Gareth Bult <garethbult>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by krishnasrinivas (Updated the item)
  • -unavailable- added by amarts (Posted a comment)
  • -unavailable- added by avati (Updated the item)
  • -unavailable- added by garethbult (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 6 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Wed 23 Apr 2008 09:45:08 PM UTCamartsOpen/ClosedOpen=>Closed
    Wed 23 Apr 2008 11:25:14 AM UTCkrishnasrinivasStatusNeed Info=>Fixed
    Sat 12 Apr 2008 02:01:50 AM UTCamartsStatusNone=>Need Info
    Tue 01 Jan 2008 07:19:16 PM UTCavatiCategoryGluster Core=>GlusterFS
      Severity3 - Normal=>4 - Important
    Tue 01 Jan 2008 07:17:31 PM UTCavatiAssigned toNone=>krishnasrinivas

    Back to the top


    Powered by Savane 3.1-cleanup1