I just noticed a very weird thing in my Raid-1 configuration. I copied a file from a directory onto my /dev/md0 device. I then mounted one of the 2 drives of md0 onto a directory and cd to it. The file was not there! I also mounted the other of the 2 drive of md0 onto another directory and cd to that one and still the file was not there. I then cd to /dev/md0 and saw the file being there again!!!! I checked my raid with mdadm --detail /dev/md0 and this is what I got: /dev/md0: Version : 00.90.00 Creation Time : Sat Oct 11 08:19:27 2003 Raid Level : raid1 Array Size : 199125568 (189.90 GiB 203.95 GB) Device Size : 199125568 (189.90 GiB 203.95 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Sat Sep 18 19:04:53 2004 State : dirty, no-errors Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Number Major Minor RaidDevice State 0 3 65 0 active sync /dev/hdb1 1 22 1 1 active sync /dev/hdc1 UUID : 03f9846c:72f50436:af213782:c8e28b96 Can someone give me some insight on why the update time is about 26 days ago?? Does that mean that my md0 is not being updated instantaneously? Thank you all for your help! Chris
On Friday, 8 October 2004 12.18, Chris Roubekas wrote:
Update Time : Sat Sep 18 19:04:53 2004 State : dirty, no-errors Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0
Number Major Minor RaidDevice State 0 3 65 0 active sync /dev/hdb1 1 22 1 1 active sync /dev/hdc1 UUID : 03f9846c:72f50436:af213782:c8e28b96
Can someone give me some insight on why the update time is about 26 days ago??
I believe that's the time your raid superblock was last updated.
Does that mean that my md0 is not being updated instantaneously?
How long did you wait after the copy? Unless you have the file system mounted with the "sync" option, it will be buffered for performance reasons. Try running "sync" in a shell and then looking in the directories again
Well it turns out that md0 is in state:dirty,no-errors for about 19 days!! Any good ideas anyone?? Is there something that I can do to change the "dirty" state?? Chris ----- Original Message ----- From: "Anders Johansson" <andjoh@rydsbo.net> To: <suse-linux-e@suse.com> Sent: Friday, October 08, 2004 1:48 PM Subject: Re: [SLE] Raid-1 Question
On Friday, 8 October 2004 12.18, Chris Roubekas wrote:
Update Time : Sat Sep 18 19:04:53 2004 State : dirty, no-errors Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0
Number Major Minor RaidDevice State 0 3 65 0 active sync /dev/hdb1 1 22 1 1 active sync /dev/hdc1 UUID : 03f9846c:72f50436:af213782:c8e28b96
Can someone give me some insight on why the update time is about 26 days ago??
I believe that's the time your raid superblock was last updated.
Does that mean that my md0 is not being updated instantaneously?
How long did you wait after the copy? Unless you have the file system mounted with the "sync" option, it will be buffered for performance reasons. Try running "sync" in a shell and then looking in the directories again
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (2)
-
Anders Johansson -
Chris Roubekas