You are not logged in.

#1 2012-06-01 20:10:09

Darkimmortal
Member
Registered: 2012-01-04
Posts: 30

Can an ext4 inode be forcefully deleted?

~ dmesg excerpts~


[Fri Jun  1 16:30:45 2012] EXT4-fs error (device dm-2): ext4_lookup:1044: inode #16260502: comm dropbox: deleted inode referenced: 16277969
[Fri Jun  1 16:30:45 2012] EXT4-fs error (device dm-2): ext4_lookup:1044: inode #16260502: comm dropbox: deleted inode referenced: 16277969
[Fri Jun  1 16:30:45 2012] EXT4-fs error (device dm-2): ext4_lookup:1044: inode #16260502: comm dropbox: deleted inode referenced: 16277969
[Fri Jun  1 17:00:39 2012] EXT4-fs error (device dm-2): ext4_lookup:1044: inode #16260502: comm dropbox: deleted inode referenced: 16277969
[Fri Jun  1 17:00:39 2012] EXT4-fs error (device dm-2): ext4_lookup:1044: inode #16260502: comm dropbox: deleted inode referenced: 16277969
[Fri Jun  1 17:00:39 2012] EXT4-fs error (device dm-2): ext4_lookup:1044: inode #16260502: comm dropbox: deleted inode referenced: 16277969
[Fri Jun  1 17:30:34 2012] EXT4-fs error (device dm-2): ext4_lookup:1044: inode #16260502: comm dropbox: deleted inode referenced: 16277969
[Fri Jun  1 17:30:34 2012] EXT4-fs error (device dm-2): ext4_lookup:1044: inode #16260502: comm dropbox: deleted inode referenced: 16277969
[Fri Jun  1 17:30:34 2012] EXT4-fs error (device dm-2): ext4_lookup:1044: inode #16260502: comm dropbox: deleted inode referenced: 16277969


~

[Fri Jun  1 08:29:14 2012] ata4.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
[Fri Jun  1 08:29:14 2012] ata4.00: irq_stat 0x40000008
[Fri Jun  1 08:29:14 2012] ata4.00: failed command: READ FPDMA QUEUED
[Fri Jun  1 08:29:14 2012] ata4.00: cmd 60/00:00:e7:47:46/01:00:01:00:00/40 tag 0 ncq 131072 in
[Fri Jun  1 08:29:14 2012]          res 41/40:00:dc:48:46/00:00:01:00:00/40 Emask 0x409 (media error) <F>
[Fri Jun  1 08:29:14 2012] ata4.00: status: { DRDY ERR }
[Fri Jun  1 08:29:14 2012] ata4.00: error: { UNC }
[Fri Jun  1 08:29:14 2012] ata4.00: configured for UDMA/133
[Fri Jun  1 08:29:14 2012] ata4: EH complete
[Fri Jun  1 08:29:16 2012] ata4.00: exception Emask 0x0 SAct 0x5 SErr 0x0 action 0x0
[Fri Jun  1 08:29:16 2012] ata4.00: irq_stat 0x40000008
[Fri Jun  1 08:29:16 2012] ata4.00: failed command: READ FPDMA QUEUED
[Fri Jun  1 08:29:16 2012] ata4.00: cmd 60/00:10:e7:47:46/01:00:01:00:00/40 tag 2 ncq 131072 in
[Fri Jun  1 08:29:16 2012]          res 41/40:00:dc:48:46/00:00:01:00:00/40 Emask 0x409 (media error) <F>
[Fri Jun  1 08:29:16 2012] ata4.00: status: { DRDY ERR }
[Fri Jun  1 08:29:16 2012] ata4.00: error: { UNC }
[Fri Jun  1 08:29:16 2012] ata4.00: configured for UDMA/133
[Fri Jun  1 08:29:16 2012] ata4: EH complete
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.3.4-2-ARCH] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint F3
Device Model:     SAMSUNG HD103SJ
Serial Number:    S246J90B317366
LU WWN Device Id: 5 0024e9 204c645a8
Firmware Version: 1AJ10001
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 6
Local Time is:    Fri Jun  1 21:08:06 2012 BST
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:                ( 9360) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        ( 156) minutes.
SCT capabilities:              (0x003f) SCT Status supported.
                                        SCT Error Recovery Control 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     0x002f   100   100   051    Pre-fail  Always       -       312
  2 Throughput_Performance  0x0026   052   052   000    Old_age   Always       -       9287
  3 Spin_Up_Time            0x0023   071   069   025    Pre-fail  Always       -       9067
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       182
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       7805
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       747
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       1
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   064   059   000    Old_age   Always       -       28 (Min/Max 14/44)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       20
199 UDMA_CRC_Error_Count    0x0036   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       332
223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       747

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%      7416         -
# 2  Short offline       Completed without error       00%      7399         -
# 3  Short offline       Completed: read failure       90%      7356         24107308
# 4  Extended offline    Completed: read failure       90%      7356         24107308
# 5  Short offline       Completed without error       00%       129         -
2 of 2 failed self-tests are outdated by newer successful extended offline self-test # 1

Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed [00% left] (0-65535)
    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.

One of my disks in a RAID 1 configuration is slowly developing more bad sectors (21 and counting), but this has been over a period of several months so I'm not particularly worried about short term failure. I have reason to believe they are due to vibration

Is there a way of telling ext4 to delete the files/inodes in question (which are disposable) without rebooting or dismounting the filesystem to run fsck?
My system is a remote headless server, and it wouldn't be the first time fsck has got stuck resulting in several hours of downtime before manual intervention.

Any attempts to rm or otherwise access the files results in 'Input/Output error', which is strange in my mind given the disk is part of a raid (mdadm based) - surely it should simply pass over to the other disk? Mdadm doesn't appear to detect any issues and considers the raid healthy

Offline

Board footer

Powered by FluxBB