fsck not solving policy violations

[Clint Byrum]

So, I've just started using a mogilefs setup, and the policy
enforcement is rather confusing..

I dumped about 1 million files into it, and somehow 79,019 of them
came out with devcount == 1 even though mindevcount is set to '2' on
that domain+class.

After running 'mogadm fsck start' I still have 79,019 files with only
one entry in file_on:

mysql> select s1.c, count(*) from (select fo.fid, count(distinct
devid) c from file_on fo group by fo.fid) s1 group by s1.c
-> ;
+---+----------+
| c | count(*) |
+---+----------+
| 1 | 79019 |
| 2 | 953623 |
| 3 | 28 |
+---+----------+

Can somebody explain why fsck wouldn't catch these and replicate them?

Thanks!

[sanados]

you verified that you do not still have entries in the table
'file_to_replicate' ?

fsck only checks if the files are around and find missing files.
For the replication to fix run 'rebalance'.

lg
Jürgen

[Clint Goudie-Nice]

Are you using mysql Master<->Master replication and more than one
tracker running?

We saw this when we has a master tracker talking to each database
server.

Clint Goudie-Nice

[Clint Byrum]

On Jul 9, 2009, at 4:33 PM, Clint Goudie-Nice wrote:

>
> Are you using mysql Master<->Master replication and more than one
> tracker running?
>
> We saw this when we has a master tracker talking to each database
> server.
>

Yes actually we do have a master<->master replication. Normally it is
active/passive, however one of the admins failed over in the middle of
a huge data conversion to do a mysql upgrade, which, I believe, caused
this issue. The replication records for those 79,019 files all had
failcount=12.

We restarted the trackers and that seemed to fix this issue. Not sure
why that would fix it though.