linux user group brescia

Eccolo:

rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=10240k,nr_inodes=127895,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=103344k,mode=755 0 0
/dev/disk/by-uuid/060e7bfe-fe33-40ca-a985-ba801f6562b0 / ext4 rw,relatime,error$
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /run/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=835000k 0 0
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0

Si, riavviato...

Il 09/03/13, Claudio Moretti<flyingstar16 a gmail.com> ha scritto:
> Qual'è il contenuto di /proc/mounts?
>
> E, domanda scema, hai provato a riavviare? :|
>
> Claudio
>
>
> 2013/3/9 Manuel Dusi <manuel.dusi a gmail.com>
>
>> ed ecco /etc/fstab:
>>
>>  / was on /dev/sda1 during installation
>> UUID=060e7bfe-fe33-40ca-a985-ba801f6562b0 /               ext4
>> errors=remount-ro 0       1
>> # swap was on /dev/sda5 during installation
>> UUID=1014dbad-e446-45db-9d9d-86a6590e4948 none            swap    sw
>>            0       0
>> /dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
>> /dev/sr1        /media/cdrom1   udf,iso9660 user,noauto     0       0
>>
>>
>>
>> Il 09/03/13, Manuel Dusi<manuel.dusi a gmail.com> ha scritto:
>> > Non so se sono fuori strada Michele,
>> > ho aperto /var/log/kern.log e vedo nella giornata di martedi 5:
>> >
>> > r  5 13:12:22 videosorveglianza kernel: [    2.404278] EXT4-fs (sda1):
>> > INFO: recovery required on readonly filesystem
>> > Mar  5 13:12:22 videosorveglianza kernel: [    2.404284] EXT4-fs
>> > (sda1): write access will be enabled during recovery
>> > Mar  5 13:12:22 videosorveglianza kernel: [   11.123408] EXT4-fs
>> > (sda1): orphan cleanup on readonly fs
>> > Mar  5 13:12:22 videosorveglianza kernel: [   11.155545] EXT4-fs
>> > (sda1): ext4_orphan_cleanup: deleting unreferenced inode 8189790
>> > Mar  5 13:12:22 videosorveglianza kernel: [   11.167267] EXT4-fs
>> > (sda1): ext4_orphan_cleanup: deleting unreferenced inode 7864332
>> > Mar  5 13:12:22 videosorveglianza kernel: [   11.167279] EXT4-fs
>> > (sda1): ext4_orphan_cleanup: deleting unreferenced inode 7864331
>> > Mar  5 13:12:22 videosorveglianza kernel: [   11.167288] EXT4-fs
>> > (sda1): ext4_orphan_cleanup: deleting unreferenced inode 7864330
>> > Mar  5 13:12:22 videosorveglianza kernel: [   11.167296] EXT4-fs
>> > (sda1): ext4_orphan_cleanup: deleting unreferenced inode 7864329
>> > Mar  5 13:12:22 videosorveglianza kernel: [   11.167310] EXT4-fs
>> > (sda1): ext4_orphan_cleanup: deleting unreferenced inode 7864328
>> > Mar  5 13:12:22 videosorveglianza kernel: [   11.167317] EXT4-fs
>> > (sda1): 6 orphan inodes deleted
>> > Mar  5 13:12:22 videosorveglianza kernel: [   11.167319] EXT4-fs
>> > (sda1): recovery complete
>> > Mar  5 13:12:22 videosorveglianza kernel: [   11.915246] EXT4-fs
>> > (sda1): mounted filesystem with ordered data mode. Opts: (null)
>> >
>> > successivamente, ai riavvii effettuati oggi vedo:
>> >
>> >  8 18:02:09 videosorveglianza kernel: [    9.658846] EXT4-fs (sda1):
>> > re-mounted. Opts: (null)
>> >   8 18:02:09 videosorveglianza kernel: [   10.083410] EXT4-fs (sda1):
>> > re-mounted. Opts: errors=remount-ro
>> >
>> > La partizione è in sda1...
>> >
>> > Se faccio un touch via ssh:
>> >
>> > root a videosorveglianza:/home/utente# touch test.txt
>> > touch: impossibile fare touch di "test.txt": Spazio esaurito sul device
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > Il 08/03/13, Michele Bonera<michele a bonera.biz> ha scritto:
>> >> Il 08/03/2013 15:34, Manuel Dusi ha scritto:
>> >>
>> >>> Aggiunta dell'ultima ora:
>> >>> - riesco da rete interna a collegarmi al webmin, sulla debian di cui
>> >>> sotto (ho fatto un saltino
>> >>> via desktop remoto sul server aziendale):
>> >>> - in ogni pagina (più o meno) webmin mi dice che non può scrivere in
>> >>> /tmp
>> >>
>> >> La butto lì: errori sulla partizione che hanno portato il kernel a
>> >> rimontare readonly?
>> >>
>> >> Bye
>> >> --
>> >> Michele Bonera
>> >> www.morrisoft.eu
>> >>
>> >> --
>> >> Info/Lamentele/Segnalazioni: andrea.gelmini a gmail.com
>> >>
>> >
>>
>> --
>> Info/Lamentele/Segnalazioni: andrea.gelmini a gmail.com
>>
>