[gl-como] ERRATA CORRIGE: "ERRORE FILE SYSTEM" - Re: Bacula ERROR
Raffaele Recalcati
lamiaposta71@gmail.com
Gio 19 Nov 2009 12:16:13 CET
Il 19 novembre 2009 12.09, Carlo Filippetto <carlo.target@tiscali.it>
ha scritto:
> Li ho trovati così.. li usavano già, mi hanno solo dato lo spazio per
> backupparci sopra!
>
> I dischi sembrano ok, tutti gli altri ambienti ci lavorano a dovere sopra
> (WINZOZ)
>
> X funzionalità SMART di montaggio intendi hot-plag? si
http://en.wikipedia.org/wiki/S.M.A.R.T.
non so però se c'è su tutti i dischi
apt-get install smartmontools
ti avverte prima che il disco ti lasci a piedi:
recalcati@recalcati-laptop:~$ sudo smartctl -i /dev/sdb
[sudo] password for recalcati:
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: FUJITSU MHZ2500BT G1
Serial Number: K70CT8825JM8
Firmware Version: 0041000C
User Capacity: 500,107,862,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 3f
Local Time is: Thu Nov 19 12:15:08 2009 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
recalcati@recalcati-laptop:~$
recalcati@recalcati-laptop:~$
recalcati@recalcati-laptop:~$ sudo smartctl -a /dev/sdb
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: FUJITSU MHZ2500BT G1
Serial Number: K70CT8825JM8
Firmware Version: 0041000C
User Capacity: 500,107,862,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 3f
Local Time is: Thu Nov 19 12:15:15 2009 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (2765) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 100 100 046 Pre-fail
Always - 2986
2 Throughput_Performance 0x0005 100 100 030 Pre-fail
Offline - 122355712
3 Spin_Up_Time 0x0003 100 100 025 Pre-fail
Always - 1
4 Start_Stop_Count 0x0032 099 099 000 Old_age
Always - 448
5 Reallocated_Sector_Ct 0x0033 100 100 024 Pre-fail
Always - 8589934592000
7 Seek_Error_Rate 0x000f 100 100 047 Pre-fail
Always - 471
8 Seek_Time_Performance 0x0005 100 100 019 Pre-fail
Offline - 0
9 Power_On_Hours 0x0032 095 095 000 Old_age
Always - 2969
10 Spin_Retry_Count 0x0013 100 100 020 Pre-fail
Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age
Always - 432
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age
Always - 36
193 Load_Cycle_Count 0x0032 100 100 000 Old_age
Always - 6786
194 Temperature_Celsius 0x0022 100 100 000 Old_age
Always - 35 (Lifetime Min/Max 11/50)
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age
Always - 8
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age
Always - 622198784
197 Current_Pending_Sector 0x0012 100 100 000 Old_age
Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age
Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age
Always - 0
200 Multi_Zone_Error_Rate 0x000f 100 100 060 Pre-fail
Always - 31606
203 Run_Out_Cancel 0x0002 100 100 000 Old_age
Always - 4827566636325
240 Head_Flying_Hours 0x003e 200 200 000 Old_age
Always - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
recalcati@recalcati-laptop:~$
----------------------------
poi bisogna saper interpretare sti numeri
>
>
>
>
> Il giorno 19 novembre 2009 11.43, Raffaele Recalcati
> <lamiaposta71@gmail.com> ha scritto:
>>
>> Il 19 novembre 2009 11.25, Carlo Filippetto <carlo.target@tiscali.it>
>> ha scritto:
>> > Visto l'errore del descrittore.. mi sono concentrato sullo starage..
>> > dall'interfaccina grafica non si riscontrano problemi, accedendo alla
>> > directory montata idem, ma accedendo direttamente in ssh allo storage
>> > (l'ho
>> > dovuto 'craccare' per abilitarla) qualcosa di strano è apparso:
>> >
>> > ecco cosa succede dal mio server:
>> > # ls VOL-weekly-*
>> > VOL-weekly-0001 VOL-weekly-0002 VOL-weekly-0003 VOL-weekly-0004
>> > VOL-weekly-0006
>> >
>> > ecco cosa succede con medesimo comando dallo storage:
>> > # ls VOL-weekly-*
>> > ls: VOL-weekly-0007: Invalid argument
>> > ls: VOL-weekly-0008: Invalid argument
>> > ls: VOL-weekly-0009: Invalid argument
>> > ls: VOL-weekly-0010: Invalid argument
>> > ls: VOL-weekly-0011: Invalid argument
>> > ls: VOL-weekly-0012: Invalid argument
>> > VOL-weekly-0001 VOL-weekly-0002 VOL-weekly-0003 VOL-weekly-0004
>> > VOL-weekly-0006
>> >
>> >
>> > col 'tab' me li vede, ed ovviamente se provo a rimuoverli otengo:
>> > # rm VOL-weekly-0007
>> > rm: unable to stat `VOL-weekly-0007': Invalid argument
>> >
>> >
>> >
>> > Quindi la domanda non è più inerente a Bacula, ma al file system.. come
>> > cancello adesso quelle cose??
>> > Il file system è un xfs
>> >
>>
>> xfs ?
>> ext4 non è meglio ?
>>
>> ma i dischi come hw sono ok, hanno le funzionalità SMART di monitoraggio?
>>
>>
>>
>> > CIAO
>> >
>> >
>> >
>> >
>> > Il giorno 19 novembre 2009 10.56, Carlo Filippetto
>> > <carlo.target@tiscali.it>
>> > ha scritto:
>> >>
>> >> Ciao a tutti,
>> >> ho un problema con Bacula che non riesco a risolvere..
>> >>
>> >> Tutti i backup vengono eseguiti su disco, ho diversi tipi di backup,
>> >> fra
>> >> cui: giornaliero, bi-settimanale e mensile. Tutti insistono sul
>> >> medesimo
>> >> storage esterno (chiamarlo storage è un eufemismo è una baracco della
>> >> Lacie
>> >> con 4 dischi in Raid 10) ed i dati finiscono sulla medesima directory,
>> >> altre
>> >> dir le differenzio solo per altri tipi di backup
>> >>
>> >> Il servizio è funzionante da ormai 5 mesi e tutto funzionava fino a 3
>> >> settimane fa quando mi si è bloccato su un backup settimanale (numerato
>> >> come
>> >> VOL-week.007) dicendo che non trovava un disco, strano.. sono tutti
>> >> li..
>> >> nessuno li ha toccati.. e questo 'errore' mi ha tenuto fermo i backup
>> >> per 3
>> >> giorni senza mandare alcun allarme. A parte non capendo cosa succedeva
>> >> dopo
>> >> vari smanettamenti, cancellazioni di job, test, ecc.. La cosa bella è
>> >> che se
>> >> manualmente accedevo al disco e toccavo qualsiasi cosa, mi si
>> >> inchiodava lo
>> >> storage.
>> >> Alla fine ho rimosso sia dal disco che dalla consolle tutti backup
>> >> vecchi
>> >> relativi a quel gruppo. Distrutto il Pool e ricreato. Bacula ha ripreso
>> >> a
>> >> funzionare correttamente.. ag oggi mi ritrovo nuovamente col medesimo
>> >> problema ed il medesimo errore.. cioè blooco sul VOL-week-007 e chiede
>> >> di
>> >> montare il disco.
>> >> Attivato i debug ottengo:
>> >>
>> >>
>> >> -------------------
>> >> bacula-sd: mount.c:643-0 Create volume label
>> >> bacula-sd: label.c:325-0 write_volume_label()
>> >> bacula-sd: label.c:346-0 New VolName=VOL-weekly-0007
>> >> bacula-sd: dev.c:303-0 open dev: type=1 dev_name="DEV-nas"
>> >> (/mnt/backup/backup) vol=VOL-weekly-0007 mode=OPEN_READ_WRITE
>> >> bacula-sd: dev.c:312-0 call open_file_device
>> >> mode=OPEN_READ_WRITE
>> >> bacula-sd: dev.c:2018-0 Enter
>> >> mount
>> >> bacula-sd: dev.c:484-0 open disk: mode=OPEN_READ_WRITE
>> >> open(/mnt/backup/backup/VOL-weekly-0007, 0x2, 0640)
>> >> bacula-sd: dev.c:491-0 open failed: dev.c:490 Could not open:
>> >> /mnt/backup/backup/VOL-weekly-0007, ERR=Descrittore di file non valido
>> >> bacula-sd: dev.c:499-0 open dev: disk fd=-1 opened, part=0/0,
>> >> part_size=0
>> >> bacula-sd: dev.c:316-0 preserve=0x0
>> >> fd=-1
>> >> bacula-sd: dev.c:303-0 open dev: type=1 dev_name="DEV-nas"
>> >> (/mnt/backup/backup) vol=VOL-weekly-0007 mode=CREATE_READ_WRITE
>> >> bacula-sd: dev.c:312-0 call open_file_device
>> >> mode=CREATE_READ_WRITE
>> >> bacula-sd: dev.c:2018-0 Enter
>> >> mount
>> >> bacula-sd: dev.c:484-0 open disk: mode=CREATE_READ_WRITE
>> >> open(/mnt/backup/backup/VOL-weekly-0007, 0x42, 0640)
>> >> bacula-sd: dev.c:491-0 open failed: dev.c:490 Could not open:
>> >> /mnt/backup/backup/VOL-weekly-0007, ERR=Descrittore di file non valido
>> >> bacula-sd: dev.c:499-0 open dev: disk fd=-1 opened, part=0/0,
>> >> part_size=0
>> >> bacula-sd: dev.c:316-0 preserve=0x0
>> >> fd=-1
>> >> bacula-sd: reserve.c:534-0 jid=1124 vol_unused: no vol on "DEV-nas"
>> >> (/mnt/backup/backup)
>> >> bacula-sd: dev.c:1848-0 Clear volhdr
>> >> vol=
>> >> bacula-sd: mount.c:648-0 write_vol_label failed. vol=VOL-weekly-0007,
>> >> pool=POOL-weekly
>> >> bacula-sd: mount.c:217-0
>> >> set_unload
>> >> bacula-sd: mount.c:220-0 goto
>> >> mount_next_vol
>> >> bacula-sd: mount.c:88-0 mount_next_vol
>> >> retry=5
>> >> bacula-sd: jcr.c:603-0 OnEntry JobStatus=R
>> >> set=M
>> >> bacula-sd: jcr.c:623-0 OnExit JobStatus=M
>> >> set=M
>> >> [Thread 0xb69b9b90 (LWP 10903) exited]
>> >> ----------------------------------------------
>> >>
>> >> qui si ferma tutto
>> >>
>> >>
>> >> Qualche consiglio? idee?
>> >>
>> >> Grazie
>> >
>> >
>> >
>> > --
>> > Mailing list info: http://lists.linux.it/listinfo/gl-como
>> >
>> >
>>
>>
>>
>> --
>> www.opensurf.it
>>
>> --
>> Mailing list info: http://lists.linux.it/listinfo/gl-como
>
>
>
> --
> Mailing list info: http://lists.linux.it/listinfo/gl-como
>
>
--
www.opensurf.it
Maggiori informazioni sulla lista
gl-como