lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3481) Building a second index on a FAT32 drive from OSX fails with OverlappingFileLockException
Date Sat, 01 Oct 2011 15:41:34 GMT


Michael McCandless commented on LUCENE-3481:

Hi Paul, could you please post a small test case showing the error?
> Building a second index on a FAT32 drive from OSX fails with OverlappingFileLockException
> -----------------------------------------------------------------------------------------
>                 Key: LUCENE-3481
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: core/index
>    Affects Versions: 3.1
>         Environment: Mac OSX 10.7 Lion with attached FAT32 disc
>            Reporter: Paul taylor
>              Labels: index, lock
> Building a new index using File(path) on a FAT32 drive from OSX.
Once the index has built but the index writer has not been closed because I want to optimize
it I create a new indexwriter to create a second completely different index. However this
fails with 
> Exception in thread "main" java.nio.channels.OverlappingFileLockException
>     at$SharedFileLockTable.checkList(
>     at$SharedFileLockTable.add(
>     at
>     at java.nio.channels.FileChannel.tryLock(
>     at
>     at
>     at org.apache.lucene.index.IndexWriter.<init>(  
> but this should not occur as I am not locking the same file, this second index is being
built in a different directory albeit with the same parent directory as the other index.
> I think the issue is specifically to do with OSX - FAT32 interaction because the problem
always occurs, but never occurs if I build the indexes on the internal Mac drive. 
> The only way I could resolve this was to remove locking using 
> File(path), NoLockFactory.getNoLockFactory() );

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message