You are viewing a plain text version of this content. The canonical link for it is here.

Posted to infrastructure-issues@apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2014/09/16 10:51:33 UTC

[jira] [Created] (INFRA-8356) ooo-wiki2-vm cron complains of no lost+found on /tmp

Gavin created INFRA-8356:
----------------------------

             Summary: ooo-wiki2-vm cron complains of no lost+found on /tmp
                 Key: INFRA-8356
                 URL: https://issues.apache.org/jira/browse/INFRA-8356
             Project: Infrastructure
          Issue Type: Bug
          Components: ColoTasks
            Reporter: Gavin
            Assignee: Gavin


/etc/cron.daily/standard:

Some local file systems lack a lost+found directory. This means if the
file system is damaged and needs to be repaired, fsck will not have
anywhere to put stray files for recovery. You should consider creating
a lost+found directory with mklost+found(8).

The following lost+found directories were not available:

/tmp/lost+found



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