AskOverflow.Dev

AskOverflow.Dev Logo AskOverflow.Dev Logo

AskOverflow.Dev Navigation

  • 主页
  • 系统&网络
  • Ubuntu
  • Unix
  • DBA
  • Computer
  • Coding
  • LangChain

Mobile menu

Close
  • 主页
  • 系统&网络
    • 最新
    • 热门
    • 标签
  • Ubuntu
    • 最新
    • 热门
    • 标签
  • Unix
    • 最新
    • 标签
  • DBA
    • 最新
    • 标签
  • Computer
    • 最新
    • 标签
  • Coding
    • 最新
    • 标签
主页 / user-4959

DaDaDom's questions

Martin Hope
DaDaDom
Asked: 2010-02-21 04:56:43 +0800 CST

LVM / Device Mapper 映射错误的设备

  • 1

我在 mdadm 创建的 raid1 上运行 LVM 设置。md2 基于 sda6 (major:minor 8:6) 和 sdb6 (8:22)。md2 是分区 9:2。md2 之上的 VG 有 4 个 LV,var、home、usr、tmp。

首先是问题:在启动时,设备映射器似乎为映射使用了错误的分区!启动后立即信息就像

~# dmsetup table
systemlvm-home: 0 4194304 linear 8:22 384
systemlvm-home: 4194304 16777216 linear 8:22 69206400
systemlvm-home: 20971520 8388608 linear 8:22 119538048
systemlvm-home: 29360128 6291456 linear 8:22 243270016
systemlvm-tmp: 0 2097152 linear 8:22 41943424
systemlvm-usr: 0 10485760 linear 8:22 20971904
systemlvm-var: 0 10485760 linear 8:22 10486144
systemlvm-var: 10485760 6291456 linear 8:22 4194688
systemlvm-var: 16777216 4194304 linear 8:22 44040576
systemlvm-var: 20971520 10485760 linear 8:22 31457664
systemlvm-var: 31457280 20971520 linear 8:22 48234880
systemlvm-var: 52428800 33554432 linear 8:22 85983616
systemlvm-var: 85983232 115343360 linear 8:22 127926656

~# cat /proc/mdstat
Personalities : [raid1]
md2 : active (auto-read-only) raid1 sda6[0]
      151798080 blocks [2/1] [U_]

md0 : active raid1 sda1[0] sdb1[1]
      96256 blocks [2/2] [UU]

md1 : active raid1 sda2[0] sdb2[1]
      2931776 blocks [2/2] [UU]

我必须手动“lvchange -an”所有 LV,将 /dev/sdb6 添加回 RAID 并重新激活 LV,然后一切都很好。但这会阻止我自动挂载分区,并且显然会导致许多其他问题。

如果一切正常,信息就像

~$ cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 sdb6[1] sda6[0]
      151798080 blocks [2/2] [UU]
...


~# dmsetup table
systemlvm-home: 0 4194304 linear 9:2 384
systemlvm-home: 4194304 16777216 linear 9:2 69206400
systemlvm-home: 20971520 8388608 linear 9:2 119538048
systemlvm-home: 29360128 6291456 linear 9:2 243270016
systemlvm-tmp: 0 2097152 linear 9:2 41943424
systemlvm-usr: 0 10485760 linear 9:2 20971904
systemlvm-var: 0 10485760 linear 9:2 10486144
systemlvm-var: 10485760 6291456 linear 9:2 4194688
systemlvm-var: 16777216 4194304 linear 9:2 44040576
systemlvm-var: 20971520 10485760 linear 9:2 31457664
systemlvm-var: 31457280 20971520 linear 9:2 48234880
systemlvm-var: 52428800 33554432 linear 9:2 85983616
systemlvm-var: 85983232 115343360 linear 9:2 127926656

我认为 LVM 出于某种原因只是“占用” /dev/sdb6 ,然后在袭击中丢失了。我尝试了 lvm.conf 中的几乎所有选项,但似乎都没有。

以下是更多信息,例如配置文件。有没有人知道这里发生了什么以及如何防止这种情况?

如果您需要任何其他信息,请告诉我

提前致谢!多米尼克

信息(关闭“修复”系统):

~# cat /etc/debian_version
5.0.4


~# uname -a
Linux kermit 2.6.26-2-686 #1 SMP Wed Feb 10 08:59:21 UTC 2010 i686 GNU/Linux


~# lvm version
  LVM version:     2.02.39 (2008-06-27)
  Library version: 1.02.27 (2008-06-25)
  Driver version:  4.13.0


~# cat /etc/mdadm/mdadm.conf
DEVICE partitions
ARRAY /dev/md1 level=raid1 num-devices=2 metadata=00.90 UUID=11e9dc6c:1da99f3f:b3088ca6:c6fe60e9
ARRAY /dev/md0 level=raid1 num-devices=2 metadata=00.90 UUID=92ed1e4b:897361d3:070682b3:3baa4fa1
ARRAY /dev/md2 level=raid1 num-devices=2 metadata=00.90 UUID=601d4642:39dc80d7:96e8bbac:649924ba


~# mount
/dev/md1 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/md0 on /boot type ext3 (rw)
/dev/mapper/systemlvm-usr on /usr type reiserfs (rw)
/dev/mapper/systemlvm-tmp on /tmp type reiserfs (rw)
/dev/mapper/systemlvm-home on /home type reiserfs (rw)
/dev/mapper/systemlvm-var on /var type reiserfs (rw)


~# grep -v ^$ /etc/lvm/lvm.conf | grep -v "#"
devices {
    dir = "/dev"
    scan = [ "/dev" ]
    preferred_names = [ ]
    filter = [ "a|/dev/md.*|", "r/.*/" ]
    cache_dir = "/etc/lvm/cache"
    cache_file_prefix = ""
    write_cache_state = 1
    sysfs_scan = 1   
    md_component_detection = 1
    ignore_suspended_devices = 0
}
log {
    verbose = 0
    syslog = 1
    overwrite = 0
    level = 0
    indent = 1
    command_names = 0
    prefix = "  "
}
backup {
    backup = 1
    backup_dir = "/etc/lvm/backup"
    archive = 1
    archive_dir = "/etc/lvm/archive"
    retain_min = 10
    retain_days = 30
}
shell {
    history_size = 100
}
global {
    umask = 077
    test = 0
    units = "h"
    activation = 1
    proc = "/proc"
    locking_type = 1
    fallback_to_clustered_locking = 1
    fallback_to_local_locking = 1
    locking_dir = "/lib/init/rw"
}
activation {
    missing_stripe_filler = "/dev/ioerror"
    reserved_stack = 256
    reserved_memory = 8192
    process_priority = -18
    mirror_region_size = 512
    readahead = "auto"
    mirror_log_fault_policy = "allocate"
    mirror_device_fault_policy = "remove"
}


:~# vgscan -vvv
        Processing: vgscan -vvv
        O_DIRECT will be used
      Setting global/locking_type to 1
      File-based locking selected.
      Setting global/locking_dir to /lib/init/rw
      Locking /lib/init/rw/P_global WB
    Wiping cache of LVM-capable devices
        /dev/block/1:0: Added to device cache
        /dev/block/1:1: Added to device cache
        /dev/block/1:10: Added to device cache
        /dev/block/1:11: Added to device cache
        /dev/block/1:12: Added to device cache
        /dev/block/1:13: Added to device cache
        /dev/block/1:14: Added to device cache
        /dev/block/1:15: Added to device cache
        /dev/block/1:2: Added to device cache
        /dev/block/1:3: Added to device cache
        /dev/block/1:4: Added to device cache
        /dev/block/1:5: Added to device cache
        /dev/block/1:6: Added to device cache
        /dev/block/1:7: Added to device cache
        /dev/block/1:8: Added to device cache
        /dev/block/1:9: Added to device cache
        /dev/block/253:0: Added to device cache
        /dev/block/253:1: Added to device cache
        /dev/block/253:2: Added to device cache
        /dev/block/253:3: Added to device cache
        /dev/block/8:0: Added to device cache
        /dev/block/8:1: Added to device cache
        /dev/block/8:16: Added to device cache
        /dev/block/8:17: Added to device cache
        /dev/block/8:18: Added to device cache
        /dev/block/8:19: Added to device cache
        /dev/block/8:2: Added to device cache
        /dev/block/8:21: Added to device cache
        /dev/block/8:22: Added to device cache
        /dev/block/8:3: Added to device cache
        /dev/block/8:5: Added to device cache
        /dev/block/8:6: Added to device cache
        /dev/block/9:0: Already in device cache
        /dev/block/9:1: Already in device cache
        /dev/block/9:2: Already in device cache
        /dev/bsg/0:0:0:0: Not a block device
        /dev/bsg/1:0:0:0: Not a block device
        /dev/bus/usb/001/001: Not a block device
        [... many more "not a block device"]
        /dev/core: Not a block device
        /dev/cpu_dma_latency: Not a block device
        /dev/disk/by-id/ata-SAMSUNG_HD160JJ_S08HJ10L507895: Aliased to /dev/block/8:16 in device cache
        /dev/disk/by-id/ata-SAMSUNG_HD160JJ_S08HJ10L507895-part1: Aliased to /dev/block/8:17 in device cache
        /dev/disk/by-id/ata-SAMSUNG_HD160JJ_S08HJ10L507895-part2: Aliased to /dev/block/8:18 in device cache
        /dev/disk/by-id/ata-SAMSUNG_HD160JJ_S08HJ10L507895-part3: Aliased to /dev/block/8:19 in device cache
        /dev/disk/by-id/ata-SAMSUNG_HD160JJ_S08HJ10L507895-part5: Aliased to /dev/block/8:21 in device cache
        /dev/disk/by-id/ata-SAMSUNG_HD160JJ_S08HJ10L507895-part6: Aliased to /dev/block/8:22 in device cache
        /dev/disk/by-id/ata-SAMSUNG_HD160JJ_S08HJ10L526800: Aliased to /dev/block/8:0 in device cache
        /dev/disk/by-id/ata-SAMSUNG_HD160JJ_S08HJ10L526800-part1: Aliased to /dev/block/8:1 in device cache
        /dev/disk/by-id/ata-SAMSUNG_HD160JJ_S08HJ10L526800-part2: Aliased to /dev/block/8:2 in device cache
        /dev/disk/by-id/ata-SAMSUNG_HD160JJ_S08HJ10L526800-part3: Aliased to /dev/block/8:3 in device cache
        /dev/disk/by-id/ata-SAMSUNG_HD160JJ_S08HJ10L526800-part5: Aliased to /dev/block/8:5 in device cache
        /dev/disk/by-id/ata-SAMSUNG_HD160JJ_S08HJ10L526800-part6: Aliased to /dev/block/8:6 in device cache
        /dev/disk/by-id/dm-name-systemlvm-home: Aliased to /dev/block/253:2 in device cache
        /dev/disk/by-id/dm-name-systemlvm-tmp: Aliased to /dev/block/253:3 in device cache
        /dev/disk/by-id/dm-name-systemlvm-usr: Aliased to /dev/block/253:1 in device cache
        /dev/disk/by-id/dm-name-systemlvm-var: Aliased to /dev/block/253:0 in device cache
        /dev/disk/by-id/dm-uuid-LVM-rL8Oq2dA7oeRYeu1orJA7Ufnb1kjOyvr25N7CRZpUMzR18NfS6zeSeAVnVT98LuU: Aliased to /dev/block/253:0 in device cache
        /dev/disk/by-id/dm-uuid-LVM-rL8Oq2dA7oeRYeu1orJA7Ufnb1kjOyvr3TpFXtLjYGEwn79IdXsSCZPl8AxmqbmQ: Aliased to /dev/block/253:1 in device cache
        /dev/disk/by-id/dm-uuid-LVM-rL8Oq2dA7oeRYeu1orJA7Ufnb1kjOyvrc5MJ4KolevMjt85PPBrQuRTkXbx6NvTi: Aliased to /dev/block/253:3 in device cache
        /dev/disk/by-id/dm-uuid-LVM-rL8Oq2dA7oeRYeu1orJA7Ufnb1kjOyvrYXrfdg5OSYDVkNeiQeQksgCI849Z2hx8: Aliased to /dev/block/253:2 in device cache
        /dev/disk/by-id/md-uuid-11e9dc6c:1da99f3f:b3088ca6:c6fe60e9: Already in device cache
        /dev/disk/by-id/md-uuid-601d4642:39dc80d7:96e8bbac:649924ba: Already in device cache
        /dev/disk/by-id/md-uuid-92ed1e4b:897361d3:070682b3:3baa4fa1: Already in device cache
        /dev/disk/by-id/scsi-SATA_SAMSUNG_HD160JJS08HJ10L507895: Aliased to /dev/block/8:16 in device cache
        /dev/disk/by-id/scsi-SATA_SAMSUNG_HD160JJS08HJ10L507895-part1: Aliased to /dev/block/8:17 in device cache
        /dev/disk/by-id/scsi-SATA_SAMSUNG_HD160JJS08HJ10L507895-part2: Aliased to /dev/block/8:18 in device cache
        /dev/disk/by-id/scsi-SATA_SAMSUNG_HD160JJS08HJ10L507895-part3: Aliased to /dev/block/8:19 in device cache
        /dev/disk/by-id/scsi-SATA_SAMSUNG_HD160JJS08HJ10L507895-part5: Aliased to /dev/block/8:21 in device cache
        /dev/disk/by-id/scsi-SATA_SAMSUNG_HD160JJS08HJ10L507895-part6: Aliased to /dev/block/8:22 in device cache
        /dev/disk/by-id/scsi-SATA_SAMSUNG_HD160JJS08HJ10L526800: Aliased to /dev/block/8:0 in device cache
        /dev/disk/by-id/scsi-SATA_SAMSUNG_HD160JJS08HJ10L526800-part1: Aliased to /dev/block/8:1 in device cache
        /dev/disk/by-id/scsi-SATA_SAMSUNG_HD160JJS08HJ10L526800-part2: Aliased to /dev/block/8:2 in device cache
        /dev/disk/by-id/scsi-SATA_SAMSUNG_HD160JJS08HJ10L526800-part3: Aliased to /dev/block/8:3 in device cache
        /dev/disk/by-id/scsi-SATA_SAMSUNG_HD160JJS08HJ10L526800-part5: Aliased to /dev/block/8:5 in device cache
        /dev/disk/by-id/scsi-SATA_SAMSUNG_HD160JJS08HJ10L526800-part6: Aliased to /dev/block/8:6 in device cache
        /dev/disk/by-path/pci-0000:00:0f.0-scsi-0:0:0:0: Aliased to /dev/block/8:0 in device cache
        /dev/disk/by-path/pci-0000:00:0f.0-scsi-0:0:0:0-part1: Aliased to /dev/block/8:1 in device cache
        /dev/disk/by-path/pci-0000:00:0f.0-scsi-0:0:0:0-part2: Aliased to /dev/block/8:2 in device cache
        /dev/disk/by-path/pci-0000:00:0f.0-scsi-0:0:0:0-part3: Aliased to /dev/block/8:3 in device cache
        /dev/disk/by-path/pci-0000:00:0f.0-scsi-0:0:0:0-part5: Aliased to /dev/block/8:5 in device cache
        /dev/disk/by-path/pci-0000:00:0f.0-scsi-0:0:0:0-part6: Aliased to /dev/block/8:6 in device cache
        /dev/disk/by-path/pci-0000:00:0f.0-scsi-1:0:0:0: Aliased to /dev/block/8:16 in device cache
        /dev/disk/by-path/pci-0000:00:0f.0-scsi-1:0:0:0-part1: Aliased to /dev/block/8:17 in device cache
        /dev/disk/by-path/pci-0000:00:0f.0-scsi-1:0:0:0-part2: Aliased to /dev/block/8:18 in device cache
        /dev/disk/by-path/pci-0000:00:0f.0-scsi-1:0:0:0-part3: Aliased to /dev/block/8:19 in device cache
        /dev/disk/by-path/pci-0000:00:0f.0-scsi-1:0:0:0-part5: Aliased to /dev/block/8:21 in device cache
        /dev/disk/by-path/pci-0000:00:0f.0-scsi-1:0:0:0-part6: Aliased to /dev/block/8:22 in device cache
        /dev/disk/by-uuid/13c1262b-e06f-40ce-b088-ce410640a6dc: Aliased to /dev/block/253:3 in device cache
        /dev/disk/by-uuid/379f57b0-2e03-414c-808a-f76160617336: Aliased to /dev/block/253:2 in device cache
        /dev/disk/by-uuid/4fb2d6d3-bd51-48d3-95ee-8e404faf243d: Already in device cache
        /dev/disk/by-uuid/5c6728ec-82c1-49c0-93c5-f6dbd5c0d659: Aliased to /dev/block/8:5 in device cache
        /dev/disk/by-uuid/a13cdfcd-2191-4185-a727-ffefaf7a382e: Aliased to /dev/block/253:1 in device cache
        /dev/disk/by-uuid/e0d5893d-ff88-412f-b753-9e3e9af3242d: Aliased to /dev/block/8:21 in device cache
        /dev/disk/by-uuid/e79c9da6-8533-4e55-93ec-208876671edc: Aliased to /dev/block/253:0 in device cache
        /dev/disk/by-uuid/f3f176f5-12f7-4af8-952a-c6ac43a6e332: Already in device cache
        /dev/dm-0: Aliased to /dev/block/253:0 in device cache (preferred name)
        /dev/dm-1: Aliased to /dev/block/253:1 in device cache (preferred name)
        /dev/dm-2: Aliased to /dev/block/253:2 in device cache (preferred name)
        /dev/dm-3: Aliased to /dev/block/253:3 in device cache (preferred name)
        /dev/fd: Symbolic link to directory
        /dev/full: Not a block device
        /dev/hpet: Not a block device
        /dev/initctl: Not a block device
        /dev/input/by-path/platform-i8042-serio-0-event-kbd: Not a block device
        /dev/input/event0: Not a block device
        /dev/input/mice: Not a block device
        /dev/kmem: Not a block device
        /dev/kmsg: Not a block device
        /dev/log: Not a block device
        /dev/loop/0: Added to device cache
        /dev/MAKEDEV: Not a block device
        /dev/mapper/control: Not a block device
        /dev/mapper/systemlvm-home: Aliased to /dev/dm-2 in device cache
        /dev/mapper/systemlvm-tmp: Aliased to /dev/dm-3 in device cache
        /dev/mapper/systemlvm-usr: Aliased to /dev/dm-1 in device cache
        /dev/mapper/systemlvm-var: Aliased to /dev/dm-0 in device cache
        /dev/md0: Already in device cache
        /dev/md1: Already in device cache
        /dev/md2: Already in device cache
        /dev/mem: Not a block device
        /dev/net/tun: Not a block device
        /dev/network_latency: Not a block device
        /dev/network_throughput: Not a block device
        /dev/null: Not a block device
        /dev/port: Not a block device
        /dev/ppp: Not a block device
        /dev/psaux: Not a block device
        /dev/ptmx: Not a block device
        /dev/pts/0: Not a block device
        /dev/ram0: Aliased to /dev/block/1:0 in device cache (preferred name)
        /dev/ram1: Aliased to /dev/block/1:1 in device cache (preferred name)
        /dev/ram10: Aliased to /dev/block/1:10 in device cache (preferred name)
        /dev/ram11: Aliased to /dev/block/1:11 in device cache (preferred name)
        /dev/ram12: Aliased to /dev/block/1:12 in device cache (preferred name)
        /dev/ram13: Aliased to /dev/block/1:13 in device cache (preferred name)
        /dev/ram14: Aliased to /dev/block/1:14 in device cache (preferred name)
        /dev/ram15: Aliased to /dev/block/1:15 in device cache (preferred name)
        /dev/ram2: Aliased to /dev/block/1:2 in device cache (preferred name)
        /dev/ram3: Aliased to /dev/block/1:3 in device cache (preferred name)
        /dev/ram4: Aliased to /dev/block/1:4 in device cache (preferred name)
        /dev/ram5: Aliased to /dev/block/1:5 in device cache (preferred name)
        /dev/ram6: Aliased to /dev/block/1:6 in device cache (preferred name)
        /dev/ram7: Aliased to /dev/block/1:7 in device cache (preferred name)
        /dev/ram8: Aliased to /dev/block/1:8 in device cache (preferred name)
        /dev/ram9: Aliased to /dev/block/1:9 in device cache (preferred name)
        /dev/random: Not a block device
        /dev/root: Already in device cache
        /dev/rtc: Not a block device
        /dev/rtc0: Not a block device
        /dev/sda: Aliased to /dev/block/8:0 in device cache (preferred name)
        /dev/sda1: Aliased to /dev/block/8:1 in device cache (preferred name)
        /dev/sda2: Aliased to /dev/block/8:2 in device cache (preferred name)
        /dev/sda3: Aliased to /dev/block/8:3 in device cache (preferred name)
        /dev/sda5: Aliased to /dev/block/8:5 in device cache (preferred name)
        /dev/sda6: Aliased to /dev/block/8:6 in device cache (preferred name)
        /dev/sdb: Aliased to /dev/block/8:16 in device cache (preferred name)
        /dev/sdb1: Aliased to /dev/block/8:17 in device cache (preferred name)
        /dev/sdb2: Aliased to /dev/block/8:18 in device cache (preferred name)
        /dev/sdb3: Aliased to /dev/block/8:19 in device cache (preferred name)
        /dev/sdb5: Aliased to /dev/block/8:21 in device cache (preferred name)
        /dev/sdb6: Aliased to /dev/block/8:22 in device cache (preferred name)
        /dev/shm/network/ifstate: Not a block device
        /dev/snapshot: Not a block device
      /dev/sndstat: stat failed: Datei oder Verzeichnis nicht gefunden
        /dev/stderr: Not a block device
        /dev/stdin: Not a block device
        /dev/stdout: Not a block device
        /dev/systemlvm/home: Aliased to /dev/dm-2 in device cache
        /dev/systemlvm/tmp: Aliased to /dev/dm-3 in device cache
        /dev/systemlvm/usr: Aliased to /dev/dm-1 in device cache
        /dev/systemlvm/var: Aliased to /dev/dm-0 in device cache
        /dev/tty: Not a block device
        /dev/tty0: Not a block device
        [... many more "not a block device"]
        /dev/vcsa6: Not a block device
        /dev/xconsole: Not a block device
        /dev/zero: Not a block device
    Wiping internal VG cache
        lvmcache: initialised VG #orphans_lvm1
        lvmcache: initialised VG #orphans_pool
        lvmcache: initialised VG #orphans_lvm2
  Reading all physical volumes.  This may take a while...
    Finding all volume groups
        /dev/ram0: Skipping (regex)
        /dev/loop/0: Skipping (sysfs)
        /dev/sda: Skipping (regex)
        Opened /dev/md0 RO
      /dev/md0: size is 192512 sectors
        Closed /dev/md0
      /dev/md0: size is 192512 sectors
        Opened /dev/md0 RW O_DIRECT
        /dev/md0: block size is 1024 bytes
        Closed /dev/md0
        Using /dev/md0
        Opened /dev/md0 RW O_DIRECT
        /dev/md0: block size is 1024 bytes
      /dev/md0: No label detected
        Closed /dev/md0
        /dev/dm-0: Skipping (regex)
        /dev/ram1: Skipping (regex)
        /dev/sda1: Skipping (regex)
        Opened /dev/md1 RO
      /dev/md1: size is 5863552 sectors
        Closed /dev/md1
      /dev/md1: size is 5863552 sectors
        Opened /dev/md1 RW O_DIRECT
        /dev/md1: block size is 4096 bytes
        Closed /dev/md1
        Using /dev/md1
        Opened /dev/md1 RW O_DIRECT
        /dev/md1: block size is 4096 bytes
      /dev/md1: No label detected
        Closed /dev/md1
        /dev/dm-1: Skipping (regex)
        /dev/ram2: Skipping (regex)
        /dev/sda2: Skipping (regex)
        Opened /dev/md2 RO
      /dev/md2: size is 303596160 sectors
        Closed /dev/md2
      /dev/md2: size is 303596160 sectors
        Opened /dev/md2 RW O_DIRECT
        /dev/md2: block size is 4096 bytes
        Closed /dev/md2
        Using /dev/md2
        Opened /dev/md2 RW O_DIRECT
        /dev/md2: block size is 4096 bytes
      /dev/md2: lvm2 label detected
        lvmcache: /dev/md2: now in VG #orphans_lvm2 (#orphans_lvm2)
        /dev/md2: Found metadata at 39936 size 2632 (in area at 2048 size 194560) for systemlvm (rL8Oq2-dA7o-eRYe-u1or-JA7U-fnb1-kjOyvr)
        lvmcache: /dev/md2: now in VG systemlvm with 1 mdas
        lvmcache: /dev/md2: setting systemlvm VGID to rL8Oq2dA7oeRYeu1orJA7Ufnb1kjOyvr
        lvmcache: /dev/md2: VG systemlvm: Set creation host to rescue.
        Closed /dev/md2
        /dev/dm-2: Skipping (regex)
        /dev/ram3: Skipping (regex)
        /dev/sda3: Skipping (regex)
        /dev/dm-3: Skipping (regex)
        /dev/ram4: Skipping (regex)
        /dev/ram5: Skipping (regex)
        /dev/sda5: Skipping (regex)
        /dev/ram6: Skipping (regex)
        /dev/sda6: Skipping (regex)
        /dev/ram7: Skipping (regex)
        /dev/ram8: Skipping (regex)
        /dev/ram9: Skipping (regex)
        /dev/ram10: Skipping (regex)
        /dev/ram11: Skipping (regex)
        /dev/ram12: Skipping (regex)
        /dev/ram13: Skipping (regex)
        /dev/ram14: Skipping (regex)
        /dev/ram15: Skipping (regex)
        /dev/sdb: Skipping (regex)
        /dev/sdb1: Skipping (regex)
        /dev/sdb2: Skipping (regex)
        /dev/sdb3: Skipping (regex)
        /dev/sdb5: Skipping (regex)
        /dev/sdb6: Skipping (regex)
      Locking /lib/init/rw/V_systemlvm RB
    Finding volume group "systemlvm"
        Opened /dev/md2 RW O_DIRECT
        /dev/md2: block size is 4096 bytes
      /dev/md2: lvm2 label detected
        lvmcache: /dev/md2: now in VG #orphans_lvm2 (#orphans_lvm2) with 1 mdas
        /dev/md2: Found metadata at 39936 size 2632 (in area at 2048 size 194560) for systemlvm (rL8Oq2-dA7o-eRYe-u1or-JA7U-fnb1-kjOyvr)
        lvmcache: /dev/md2: now in VG systemlvm with 1 mdas
        lvmcache: /dev/md2: setting systemlvm VGID to rL8Oq2dA7oeRYeu1orJA7Ufnb1kjOyvr
        lvmcache: /dev/md2: VG systemlvm: Set creation host to rescue.
        Using cached label for /dev/md2
        Read systemlvm metadata (19) from /dev/md2 at 39936 size 2632
        /dev/md2 0:      0     16: home(0:0)
        /dev/md2 1:     16     24: var(40:0)
        /dev/md2 2:     40     40: var(0:0)
        /dev/md2 3:     80     40: usr(0:0)
        /dev/md2 4:    120     40: var(80:0)
        /dev/md2 5:    160      8: tmp(0:0)
        /dev/md2 6:    168     16: var(64:0)
        /dev/md2 7:    184     80: var(120:0)
        /dev/md2 8:    264     64: home(16:0)
        /dev/md2 9:    328    128: var(200:0)
        /dev/md2 10:    456     32: home(80:0)
        /dev/md2 11:    488    440: var(328:0)
        /dev/md2 12:    928     24: home(112:0)
        /dev/md2 13:    952    206: NULL(0:0)
  Found volume group "systemlvm" using metadata type lvm2
        Read volume group systemlvm from /etc/lvm/backup/systemlvm
      Unlocking /lib/init/rw/V_systemlvm
        Closed /dev/md2
      Unlocking /lib/init/rw/P_global


~# vgdisplay
  --- Volume group ---
  VG Name               systemlvm
  System ID            
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  19
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                4
  Open LV               4
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               144,75 GB
  PE Size               128,00 MB
  Total PE              1158
  Alloc PE / Size       952 / 119,00 GB
  Free  PE / Size       206 / 25,75 GB
  VG UUID               rL8Oq2-dA7o-eRYe-u1or-JA7U-fnb1-kjOyvr


~# pvdisplay
  --- Physical volume ---
  PV Name               /dev/md2
  VG Name               systemlvm
  PV Size               144,77 GB / not usable 16,31 MB
  Allocatable           yes
  PE Size (KByte)       131072
  Total PE              1158
  Free PE               206
  Allocated PE          952
  PV UUID               ZSAzP5-iBvr-L7jy-wB8T-AiWz-0g3m-HLK66Y


:~# lvdisplay
  --- Logical volume ---
  LV Name                /dev/systemlvm/home
  VG Name                systemlvm
  LV UUID                YXrfdg-5OSY-DVkN-eiQe-Qksg-CI84-9Z2hx8
  LV Write Access        read/write
  LV Status              available
  # open                 2
  LV Size                17,00 GB
  Current LE             136
  Segments               4
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:2

  --- Logical volume ---
  LV Name                /dev/systemlvm/var
  VG Name                systemlvm
  LV UUID                25N7CR-ZpUM-zR18-NfS6-zeSe-AVnV-T98LuU
  LV Write Access        read/write
  LV Status              available
  # open                 2
  LV Size                96,00 GB
  Current LE             768
  Segments               7
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0

  --- Logical volume ---
  LV Name                /dev/systemlvm/usr
  VG Name                systemlvm
  LV UUID                3TpFXt-LjYG-Ewn7-9IdX-sSCZ-Pl8A-xmqbmQ
  LV Write Access        read/write
  LV Status              available
  # open                 2
  LV Size                5,00 GB
  Current LE             40
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:1

  --- Logical volume ---
  LV Name                /dev/systemlvm/tmp
  VG Name                systemlvm
  LV UUID                c5MJ4K-olev-Mjt8-5PPB-rQuR-TkXb-x6NvTi
  LV Write Access        read/write
  LV Status              available
  # open                 2
  LV Size                1,00 GB
  Current LE             8
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:3
lvm mdadm
  • 5 个回答
  • 5496 Views
Martin Hope
DaDaDom
Asked: 2010-02-07 18:28:57 +0800 CST

rdiff-backup 恢复没有子目录的目录

  • 1

有没有办法恢复 rdiff-backup 生成的备份但跳过子目录?假设我已经备份了和/dir,我只想恢复和,跳过。我试过了,但 --exclude 似乎被忽略了,尽管它正在被解析。/dir/subA/dir/subB/dir/dir/subB/dir/subArdiff-backup -r now --exclude /dir/subA /dir server::/dir

为什么我要这样做?好吧,我不能/dir一次恢复整个,因为它太大了,无法在 24 小时内恢复,之后我失去了拨号连接。相反,它也不起作用,首先恢复子目录,然后恢复主目录,因为子目录也正在再次恢复。

backup restore rdiff-backup
  • 2 个回答
  • 2242 Views
Martin Hope
DaDaDom
Asked: 2010-02-05 10:48:24 +0800 CST

Debian下mysql的权限问题

  • 0

在经历了巨大的硬盘崩溃(与 Debian 的 LVM 更新有关,而不是硬件)之后,我面临下一个问题:在那次崩溃后我尝试重新安装 mysql 并dpkg --ignore-depends ... --purge mysql-...在机器上做了一个。没有 MySQL,只有依赖包:

kermit:~# dpkg -l | grep -i mysql
ii  courier-authlib-mysql
ii  libdbd-mysql-perl
ii  libpam-mysql
ii  php5-mysql
ii  postfix-mysql
ii  proftpd-mod-mysql

没有运行 mysql 进程,没有像 /var/lib/mysql 这样的目录,什么都没有。基本上(这就是我的想法)一个全新安装的mysql。但不,这并不容易。一步步:

kermit:/var/cache/apt/archives# ls mysql-*
mysql-client_5.1.43-0.dotdeb.1_all.deb       mysql-common_5.1.43-0.dotdeb.1_all.deb  mysql-server-5.1_5.1.43-0.dotdeb.1_i386.deb
mysql-client-5.1_5.1.43-0.dotdeb.1_i386.deb  mysql-server_5.1.43-0.dotdeb.1_all.deb
kermit:/var/cache/apt/archives# dpkg -i mysql-*.deb
[...]
Stopping MySQL database server: mysqld.
100204 19:37:47 [Note] Plugin 'FEDERATED' is disabled.
100204 19:37:47  InnoDB: Started; log sequence number 0 44233
ERROR: 1146  Table 'mysql.user' doesn't exist
100204 19:37:47 [ERROR] Aborting

100204 19:37:47  InnoDB: Starting shutdown...
100204 19:37:53  InnoDB: Shutdown completed; log sequence number 0 44233
100204 19:37:53 [Note] /usr/sbin/mysqld: Shutdown complete

Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
invoke-rc.d: initscript mysql, action "start" failed.
[...]

繁荣!不好。中只有空文件,. 中/var/log/mysql/没有任何内容/var/log/mysql.*。但是看哪,有/var/log/daemon.log:

Feb  4 19:38:13 kermit mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Feb  4 19:38:13 kermit mysqld: 100204 19:38:13 [Note] Plugin 'FEDERATED' is disabled.
Feb  4 19:38:13 kermit mysqld: /usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist
Feb  4 19:38:13 kermit mysqld: 100204 19:38:13 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
Feb  4 19:38:13 kermit mysqld: 100204 19:38:13  InnoDB: Started; log sequence number 0 44233
Feb  4 19:38:13 kermit mysqld: 100204 19:38:13 [ERROR] Can't start server : Bind on unix socket: Permission denied
Feb  4 19:38:13 kermit mysqld: 100204 19:38:13 [ERROR] Do you already have another mysqld server running on socket: /var/run/mysqld/mysqld.sock ?
Feb  4 19:38:13 kermit mysqld: 100204 19:38:13 [ERROR] Aborting
Feb  4 19:38:13 kermit mysqld: 
Feb  4 19:38:13 kermit mysqld: 100204 19:38:13  InnoDB: Starting shutdown...
Feb  4 19:38:18 kermit mysqld: 100204 19:38:18  InnoDB: Shutdown completed; log sequence number 0 44233
Feb  4 19:38:18 kermit mysqld: 100204 19:38:18 [Note] /usr/sbin/mysqld: Shutdown complete
Feb  4 19:38:18 kermit mysqld: 
Feb  4 19:38:18 kermit mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
Feb  4 19:38:27 kermit /etc/init.d/mysql[9108]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Feb  4 19:38:27 kermit /etc/init.d/mysql[9108]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
Feb  4 19:38:27 kermit /etc/init.d/mysql[9108]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Feb  4 19:38:27 kermit /etc/init.d/mysql[9108]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Feb  4 19:38:27 kermit /etc/init.d/mysql[9108]: 

好吧,确实那里没有文件:

kermit:~# ls -larth /var/lib/mysql/ /var/lib/mysql/mysql/
/var/lib/mysql/mysql/:
insgesamt 0
drwx------ 2 mysql mysql  48  4. Feb 19:38 .
drwx------ 3 mysql mysql 192  4. Feb 19:38 ..

/var/lib/mysql/:
insgesamt 21M
-rw-rw----  1 mysql mysql 5,0M  4. Feb 19:35 ib_logfile1
-rw-r--r--  1 mysql mysql    0  4. Feb 19:37 debian-5.1.flag
drwxr-xr-x 42 root  root  1,1K  4. Feb 19:37 ..
drwx------  2 mysql mysql   48  4. Feb 19:38 mysql
drwx------  3 mysql mysql  192  4. Feb 19:38 .
-rw-rw----  1 mysql mysql 5,0M  4. Feb 19:38 ib_logfile0
-rw-rw----  1 mysql mysql  10M  4. Feb 19:38 ibdata1

还有一些目录:

kermit:/etc/mysql# ls -larth /var/run/mysqld/
insgesamt 512
drwxr-xr-x 13 root  root 672  4. Feb 19:35 ..
drwxr-xr-x  2 mysql root  48  4. Feb 19:35 .

kermit:~# ls -larth /var/log/mysql*
-rw-r----- 1 mysql adm  0  4. Feb 19:37 /var/log/mysql.log
-rw-r----- 1 mysql adm  0  4. Feb 19:37 /var/log/mysql.err

/var/log/mysql:
insgesamt 4,0K
drwxr-xr-x 15 root  root 4,3K  4. Feb 19:35 ..
drwxr-s---  2 mysql adm    48  4. Feb 19:35 .

配置:

kermit:/etc/mysql# grep -v ^# my.cnf  | grep -v "^$"
[client]
port        = 3306
socket      = /var/run/mysqld/mysqld.sock
[mysqld_safe]
socket      = /var/run/mysqld/mysqld.sock
nice        = 0
[mysqld]
user        = mysql
pid-file    = /var/run/mysqld/mysqld.pid
socket      = /var/run/mysqld/mysqld.sock
port        = 3306
basedir     = /usr
datadir     = /var/lib/mysql
tmpdir      = /tmp
language    = /usr/share/mysql/english
skip-external-locking
bind-address        = 127.0.0.1
key_buffer      = 16M
max_allowed_packet  = 16M
thread_stack        = 192K
thread_cache_size       = 8
myisam-recover         = BACKUP
query_cache_limit   = 1M
query_cache_size        = 16M
expire_logs_days    = 10
max_binlog_size         = 100M
[mysqldump]
quick
quote-names
max_allowed_packet  = 16M
[mysql]
[isamchk]
key_buffer      = 16M
!includedir /etc/mysql/conf.d/

有人知道吗?

谢谢!

mysql debian permissions
  • 3 个回答
  • 2878 Views
Martin Hope
DaDaDom
Asked: 2010-02-03 22:20:37 +0800 CST

lvm上的reiserfsck

  • 2

似乎我的文件系统在上次重新启动服务器时以某种方式损坏了。我不能再fsck有一些逻辑卷了。设置:

root@rescue ~ # cat /mnt/rescue/etc/fstab 
proc /proc proc defaults 0 0
/dev/md0 /boot ext3 defaults 0 2
/dev/md1 / ext3 defaults,errors=remount-ro 0 1

/dev/systemlvm/home /home reiserfs defaults 0 0
/dev/systemlvm/usr /usr reiserfs defaults   0 0
/dev/systemlvm/var /var reiserfs defaults   0 0
/dev/systemlvm/tmp /tmp reiserfs noexec,nosuid 0 2

/dev/sda5 none swap defaults,pri=1 0 0
/dev/sdb5 none swap defaults,pri=1 0 0

[更新] 第一个问题:我应该检查哪些“部分”是否有坏块?逻辑卷,底层/dev/md还是/dev/sdx下面?做我正在做的事情是正确的吗? [/UPDATE] 检查 /dev/systemlvm/usr 时的错误信息:

root@rescue ~ # reiserfsck /dev/systemlvm/usr 
reiserfsck 3.6.19 (2003 www.namesys.com)
[...]
Will read-only check consistency of the filesystem on /dev/systemlvm/usr
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Wed Feb  3 07:10:55 2010
###########
Replaying journal..
Reiserfs journal '/dev/systemlvm/usr' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..

Bad root block 0. (--rebuild-tree did not complete)

Aborted

到目前为止,让我们尝试一下--rebuild-tree:

root@rescue ~ # reiserfsck --rebuild-tree /dev/systemlvm/usr 
reiserfsck 3.6.19 (2003 www.namesys.com)

[...]

Will rebuild the filesystem (/dev/systemlvm/usr) tree
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
Replaying journal..
Reiserfs journal '/dev/systemlvm/usr' in blocks [18..8211]: 0 transactions replayed
###########
reiserfsck --rebuild-tree started at Wed Feb  3 07:12:27 2010
###########
Pass 0:
####### Pass 0 #######
Loading on-disk bitmap .. ok, 269716 blocks marked used
Skipping 8250 blocks (super block, journal, bitmaps) 261466 blocks will be read
0%....20%....40%....60%....80%....100%                       left 0, 11368 /sec
52919 directory entries were hashed with "r5" hash.
        "r5" hash is selected
Flushing..finished
        Read blocks (but not data blocks) 261466
                Leaves among those 13086
                Objectids found 53697

Pass 1 (will try to insert 13086 leaves):
####### Pass 1 #######
Looking for allocable blocks .. finished
0%                                                           left 12675, 0 /sec
The problem has occurred looks like a hardware problem (perhaps
memory). Send us the bug report only if the second run dies at
the same place with the same block number.

mark_block_used: (39508) used already
Aborted

坏的。但是,让我们再做一次,如前所述:

[...]
Flushing..finished
        Read blocks (but not data blocks) 261466
                Leaves among those 13085
                Objectids found 54305

Pass 1 (will try to insert 13085 leaves):
####### Pass 1 #######
Looking for allocable blocks .. finished
0%...                                                      left 12127, 958 /sec
The problem has occurred looks like a hardware problem (perhaps
memory). Send us the bug report only if the second run dies at
the same place with the same block number.

build_the_tree: Nothing but leaves are expected. Block 196736 - internal

Aborted

每次都会发生同样的情况,只有实际的错误消息会发生变化。有时我得到mark_block_used: (somenumber) used already,其他时候块号改变。好像有些东西真的坏了。我有没有机会让分区再次工作?这是我无法直接物理访问的服务器(托管服务器)。

提前致谢!

lvm reiserfs
  • 1 个回答
  • 1170 Views

Sidebar

Stats

  • 问题 205573
  • 回答 270741
  • 最佳答案 135370
  • 用户 68524
  • 热门
  • 回答
  • Marko Smith

    新安装后 postgres 的默认超级用户用户名/密码是什么?

    • 5 个回答
  • Marko Smith

    SFTP 使用什么端口?

    • 6 个回答
  • Marko Smith

    命令行列出 Windows Active Directory 组中的用户?

    • 9 个回答
  • Marko Smith

    什么是 Pem 文件,它与其他 OpenSSL 生成的密钥文件格式有何不同?

    • 3 个回答
  • Marko Smith

    如何确定bash变量是否为空?

    • 15 个回答
  • Martin Hope
    Tom Feiner 如何按大小对 du -h 输出进行排序 2009-02-26 05:42:42 +0800 CST
  • Martin Hope
    Noah Goodrich 什么是 Pem 文件,它与其他 OpenSSL 生成的密钥文件格式有何不同? 2009-05-19 18:24:42 +0800 CST
  • Martin Hope
    Brent 如何确定bash变量是否为空? 2009-05-13 09:54:48 +0800 CST
  • Martin Hope
    cletus 您如何找到在 Windows 中打开文件的进程? 2009-05-01 16:47:16 +0800 CST

热门标签

linux nginx windows networking ubuntu domain-name-system amazon-web-services active-directory apache-2.4 ssh

Explore

  • 主页
  • 问题
    • 最新
    • 热门
  • 标签
  • 帮助

Footer

AskOverflow.Dev

关于我们

  • 关于我们
  • 联系我们

Legal Stuff

  • Privacy Policy

Language

  • Pt
  • Server
  • Unix

© 2023 AskOverflow.DEV All Rights Reserve