无法挂载XFS – 糟糕的超级块

请记住，我很小白，不知道我在做什么。 我们有一个716iS iSCSI raid的戴尔PowerEdge 420。 networking连接掉在磁盘使用中，我们不能再挂载。 我试过xfs_check / dev / sdf

Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .....<> ..... found candidate secondary superblock unable to verify superblock continuing... .....<> ..... 

但它永远无法find有效的超级块。 同理：

 xfs_repair -n /dev/sdf Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... 

这没有find有效的超级块。

我能做些什么来恢复这个文件系统？

• xfsdump：跨越多个驱动器
• 可以把更大的磁盘放在LSIarrays中？
• XFS是否支持默认配额？
• 在Linux上存储照片的最佳文件系统
• 为什么用ec2-consistent-snapshot调用xfs_freeze时不能find这个目录？

编辑：util fdisk不支持GPT。 使用GNU Parted。 这里是parted-parted -l / dev / sdf

  Model: DELL PERC H310 (scsi) Disk /dev/sda: 500GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 525MB 524MB primary ext4 boot 2 525MB 500GB 499GB primary lvm Model: JetStor JetStor -VOL1 - (scsi) Disk /dev/sdb: 39.0TB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 1049kB 39.0TB 39.0TB primary Model: JetStor JetStor -VOL2 (scsi) Disk /dev/sdc: 52.0TB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 1049kB 52.0TB 52.0TB primary Model: JetStor JetStor -VOL1 - (scsi) Disk /dev/sdd: 39.0TB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 1049kB 39.0TB 39.0TB primary Model: JetStor JetStor -VOL2 (scsi) Disk /dev/sde: 52.0TB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 1049kB 52.0TB 52.0TB primary Model: AC&Ncorp JetStor (scsi) Disk /dev/sdf: 52.0TB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 1049kB 52.0TB 52.0TB primary Error: /dev/mapper/mpathcp1: unrecognised disk label Model: Linux device-mapper (multipath) (dm) Disk /dev/mapper/mpathc: 52.0TB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 1049kB 52.0TB 52.0TB primary Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_cfile-lv_var: 105GB Sector size (logical/physical): 512B/512B Partition Table: loop Number Start End Size File system Flags 1 0.00B 105GB 105GB ext4 Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_jet716s_vol2-lv_jet716sV2a: 37.7TB Sector size (logical/physical): 512B/512B Partition Table: loop Number Start End Size File system Flags 1 0.00B 37.7TB 37.7TB xfs Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_jet716s-lv_jet716s_jet: 39.0TB Sector size (logical/physical): 512B/512B Partition Table: loop Number Start End Size File system Flags 1 0.00B 39.0TB 39.0TB xfs Error: /dev/mapper/mpathbp1: unrecognised disk label Error: /dev/mapper/mpathdp1: unrecognised disk label Model: Linux device-mapper (multipath) (dm) Disk /dev/mapper/mpathb: 39.0TB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 1049kB 39.0TB 39.0TB primary Model: Linux device-mapper (multipath) (dm) Disk /dev/mapper/mpathd: 52.0TB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 1049kB 52.0TB 52.0TB primary Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_cfile-lv_swap: 33.8GB Sector size (logical/physical): 512B/512B Partition Table: loop Number Start End Size File system Flags 1 0.00B 33.8GB 33.8GB linux-swap(v1) Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_cfile-lv_root: 53.7GB Sector size (logical/physical): 512B/512B Partition Table: loop Number Start End Size File system Flags 1 0.00B 53.7GB 53.7GB ext4 

edit2：这是文件-s。

 file -s /dev/sdf{,1,2,3,4,5,6} /dev/sdf: x86 boot sector; partition 1: ID=0xee, starthead 0, startsector 1, 4294967295 sectors, extended partition table (last)\011, code offset 0x0 /dev/sdf1: cannot open `/dev/sdf1' (No such file or directory) /dev/sdf2: cannot open `/dev/sdf2' (No such file or directory) /dev/sdf3: cannot open `/dev/sdf3' (No such file or directory) /dev/sdf4: cannot open `/dev/sdf4' (No such file or directory) /dev/sdf5: cannot open `/dev/sdf5' (No such file or directory) /dev/sdf6: cannot open `/dev/sdf6' (No such file or directory) 

编辑3：这是multipath -l的输出

  mpathd (35001b4d0189b4801) dm-2 JetStor,JetStor -VOL2 size=47T features='0' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=0 status=active |- 7:0:0:1 sdc 8:32 active undef running `- 7:0:1:1 sde 8:64 active undef running mpathc (32029001378917600) dm-9 AC&Ncorp,JetStor size=47T features='0' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=0 status=active `- 8:0:0:0 sdf 8:80 active undef running mpathb (35001b4d0189b4800) dm-3 JetStor,JetStor -VOL1 - size=35T features='0' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=0 status=active |- 7:0:0:0 sdb 8:16 active undef running `- 7:0:1:0 sdd 8:48 active undef running 

和/etc/multipath.conf的内容

  # This is a basic configuration file with some examples, for device mapper # multipath. # For a complete list of the default configuration values, see # /usr/share/doc/device-mapper-multipath-0.4.9/multipath.conf.defaults # For a list of configuration options with descriptions, see # /usr/share/doc/device-mapper-multipath-0.4.9/multipath.conf.annotated # # REMEMBER: After updating multipath.conf, you must run # # service multipathd reload # # for the changes to take effect in multipathd ## By default, devices with vendor = "IBM" and product = "S/390.*" are ## blacklisted. To enable mulitpathing on these devies, uncomment the ## following lines. #blacklist_exceptions { # device { # vendor "IBM" # product "S/390.*" # } #} ## Use user friendly names, instead of using WWIDs as names. #defaults { # user_friendly_names yes #} ## ## Here is an example of how to configure some standard options. ## # 5/21/14: uncommented this defaults { udev_dir /dev polling_interval 10 path_selector "round-robin 0" path_grouping_policy multibus getuid_callout "/lib/udev/scsi_id --whitelisted --device=/dev/%n" prio alua path_checker readsector0 rr_min_io 100 max_fds 8192 rr_weight priorities failback immediate no_path_retry fail user_friendly_names yes } ## ## The wwid line in the following blacklist section is shown as an example ## of how to blacklist devices by wwid. The 2 devnode lines are the ## compiled in default blacklist. If you want to blacklist entire types ## of devices, such as all scsi devices, you should use a devnode line. ## However, if you want to blacklist specific devices, you should use ## a wwid line. Since there is no guarantee that a specific device will ## not change names on reboot (from /dev/sda to /dev/sdb for example) ## devnode lines are not recommended for blacklisting specific devices. ## #blacklist { # wwid 26353900f02796769 # devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" # devnode "^hd[az]" #} #multipaths { # multipath { # wwid 3600508b4000156d700012000000b0000 # alias yellow # path_grouping_policy multibus # path_checker readsector0 # path_selector "round-robin 0" # failback manual # rr_weight priorities # no_path_retry 5 # } # multipath { # wwid 1DEC_____321816758474 # alias red # } #} #devices { # device { # vendor "COMPAQ " # product "HSV110 (C)COMPAQ" # path_grouping_policy multibus # getuid_callout "/lib/udev/scsi_id --whitelisted --device=/dev/%n" # path_checker readsector0 # path_selector "round-robin 0" # hardware_handler "0" # failback 15 # rr_weight priorities # no_path_retry queue # } # device { # vendor "COMPAQ " # product "MSA1000 " # path_grouping_policy multibus # } #} blacklist { } 

还有另一个SCSIarrays，这可能是它改变设备的原因。