hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei-Chiu Chuang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12583) Sundry symlink problems on Solaris
Date Wed, 25 Nov 2015 23:01:11 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027753#comment-15027753
] 

Wei-Chiu Chuang commented on HADOOP-12583:
------------------------------------------

I don't have a Solaris machine, but from the log it appears that on Solaris, if you set timestamp
of a file through its symbolic link, the timestamp of the symbolic link is also updated?

> Sundry symlink problems on Solaris
> ----------------------------------
>
>                 Key: HADOOP-12583
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12583
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs
>    Affects Versions: 2.7.1
>         Environment: Solaris
>            Reporter: Alan Burlison
>
> There are various filesystem test failures on Solaris, all related to symlinks:
> {code}
> TestSymlinkLocalFSFileContext>TestSymlinkLocalFS.testDanglingLink:156 expected:<[alanbur]>
but was:<[]>
> TestSymlinkLocalFSFileContext>TestSymlinkLocalFS.testSetTimesSymlinkToDir:233->SymlinkBaseTest.testSetTimesSymlinkToDir:1391
expected:<1447788288000> but was:<3000>
> TestSymlinkLocalFSFileContext>TestSymlinkLocalFS.testSetTimesSymlinkToFile:227->SymlinkBaseTest.testSetTimesSymlinkToFile:1376
expected:<1447788290000> but was:<3000>
> TestSymlinkLocalFSFileSystem>TestSymlinkLocalFS.testDanglingLink:156 expected:<[alanbur]>
but was:<[]>
> TestSymlinkLocalFSFileSystem>TestSymlinkLocalFS.testSetTimesSymlinkToDir:233->SymlinkBaseTest.testSetTimesSymlinkToDir:1391
expected:<1447788416000> but was:<3000>
> TestSymlinkLocalFSFileSystem>TestSymlinkLocalFS.testSetTimesSymlinkToFile:227->SymlinkBaseTest.testSetTimesSymlinkToFile:1376
expected:<1447788417000> but was:<3000>
> {code}
> I'm not sure what the root cause is, most likely Linux-specific assumptions about how
symlinks behave. Further investigation needed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message