On 07.01.16 12:16, Nicola Scattolin wrote:
> i tried to create a directory on backuppc/pc and i get the error
>
> "mkdir: cannot create directory `aaa': Read-only file system"
>
Looks like your filesystem has been mounted read-only. Check that with the
'mount' command.
Another question why the
On 07.01.16 11:27, Nicola Scattolin wrote:
> I try to launch it manually and i get the following error .
>
> Starting backuppc...2016-01-07 09:23:07 Can't create a test hardlink
> between a file in /var/lib/backuppc/pc and /var/lib/backuppc/cpool.
> Either these are different file systems, or this
On 07.01.16 12:02, Nicola Scattolin wrote:
> no the file sistem has many inode free and the file system usage is under 70%
>
Do you have tried to create test hardlinks using 'ls -ld' (with the backuppc
user credentials)?
On 07.01.16 12:31, Nicola Scattolin wrote:
> i have looked at the disks with smartctl -H and they look ok
I'd never seen anything besides "result: PASSED" even on failing hard-disks.
You should better look at the SMART error log and SMART attributes.
no the file sistem has many inode free and the file system usage is
under 70%
Il 07/01/2016 10:00, Alexander Moisseev ha scritto:
On 07.01.16 11:27, Nicola Scattolin wrote:
I try to launch it manually and i get the following error .
Starting backuppc...2016-01-07 09:23:07 Can't create a test
On Thu, Jan 7, 2016 at 3:31 AM, Nicola Scattolin wrote:
>
> i have looked at the disks with smartctl -H and they look ok, i will now look
> to see why it was mounted read only.
>
Check /var/log/messages for scsi related errors. That - or some
filesystem errors - can trigger
On 08/01/16 04:24, Les Mikesell wrote:
> On Thu, Jan 7, 2016 at 3:31 AM, Nicola Scattolin wrote:
>> i have looked at the disks with smartctl -H and they look ok, i will now
>> look to see why it was mounted read only.
>>
> Check /var/log/messages for scsi related errors. That