xfs
[Top] [All Lists]

Re: XFS recovery on root filesystem

To: Sarwer Zafiruddin <sarwer.zafiruddin@xxxxxxxx>
Subject: Re: XFS recovery on root filesystem
From: Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>
Date: Thu, 25 Apr 2002 17:24:41 +0200
>received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id C602B57306; Thu, 25 Apr 2002 17:24:42 +0200 (CEST)
Cc: linux-xfs@xxxxxxxxxxx
Organization: Sauter AG, Basel
References: <Pine.LNX.4.33.0204251049450.1201-100000@xxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
Sarwer Zafiruddin schrieb:
> 
> Hello,
> 
> I was curious about somthing.  I have a system running the RedHat
> distribution of XFS 1.1 on a system.  When I upgraded the RPM's and the
> redhat kernel (I recompiled the kernel using the SGI XFS kernel SRPM on my
> system) and rebooted the system, I noticed the following messages in my
> dmesg log (I rebooted the system remotely):
> 
> XFS mounting filesystem ide0(3,2)
> XFS: WARNING: recovery required on readonly filesystem.
> XFS: write access will be enabled during mount.
> Starting XFS recovery on filesystem: ide0(3,2) (dev: 3/2)
> Ending XFS recovery on filesystem: ide0(3,2) (dev: 3/2)
> VFS: Mounted root (xfs filesystem) readonly.
> 
> None of my other filesystems performed a recovery

I guess you have also updated glibc. IIRC when updating glibc, the root
fs can not be unmounted properly (remount readonly) on shutdown and
therefore you'll notice recovery on the first boot after glibc upgrade.
It has always been like this and was very annoying with big root fs on
ext2 :) I'm sure it's not kernel related.

Can you confirm this?

-Simon

> 
> XFS mounting filesystem ide0(3,1)
> XFS mounting filesystem ide0(3,10)
> XFS mounting filesystem ide0(3,7)
> XFS mounting filesystem ide0(3,8)
> XFS mounting filesystem ide0(3,3)
> XFS mounting filesystem ide0(3,9)
> 
> I was runing the SGI XFS 1.0.2 (using installer) Redhat 7.2, and the
> system was up for more than 120 days before the reboot.
> 
> QUESTION #1:
> 
> What could have prompted the recovery???  Un-clean unmount during the
> reboot???  The fact the upgrade process requires a xfs recovery to be
> performed on the root fs???  Could it be similar to ext2 where if the fs
> has not been check in X amount of days it does a fsck equivlent???
> 
> QUESTION #2:
> 
> Should I bring my system down to maintaince, boot off CD and run
> xfs_repair on my root filesystem to make sure everything is consistant?
> 
> Here is some extra info...
> 
> [root@some /]# uname -a
> Linux some.host.name 2.4.9-31SGI_XFS_1.1 #1 Thu Apr 18 14:36:41 EDT 2002 i686 
> unknown
> [root@some /]# rpm -qa | grep -i xfs
> xfsdump-2.0.1-0
> kernel-source-2.4.9-31SGI_XFS_1.1
> anaconda-7.2-11XFS
> kernel-headers-2.4.9-31SGI_XFS_1.1
> kernel-2.4.9-31SGI_XFS_1.1
> anaconda-runtime-7.2-11XFS
> xfsprogs-devel-2.0.3-0
> kernel-doc-2.4.9-31SGI_XFS_1.1
> kernel-2.4.9-13SGI_XFS_1.0.2
> xfsprogs-2.0.3-0
> [root@some /]# kgcc -v
> Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs
> gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
> 
> full dmesg...
> 
> Linux version 2.4.9-31SGI_XFS_1.1 (root@xxxxxxxxxxxxxx) (gcc version 
> egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Thu Apr 18 14:36:41 EDT 
> 2002
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
>  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 0000000006ffd000 (usable)
>  BIOS-e820: 0000000006ffd000 - 0000000006fff000 (ACPI data)
>  BIOS-e820: 0000000006fff000 - 0000000007000000 (ACPI NVS)
>  BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
> On node 0 totalpages: 28669
> zone(0): 4096 pages.
> zone(1): 24573 pages.
> zone(2): 0 pages.
> Kernel command line: auto BOOT_IMAGE=linux ro root=302 
> BOOT_FILE=/boot/vmlinuz-2.4.9-31SGI_XFS_1.1
> Initializing CPU#0
> Detected 801.835 MHz processor.
> Console: colour VGA+ 80x25
> Calibrating delay loop... 1599.07 BogoMIPS
> Memory: 108408k/114676k available (2521k kernel code, 5116k reserved, 97k 
> data, 224k init, 0k highmem)
> kdb version 2.1 by Scott Lurndal, Keith Owens. Copyright SGI, All Rights 
> Reserved
> Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
> Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
> Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
> Page-cache hash table entries: 32768 (order: 6, 262144 bytes)
> CPU: Before vendor init, caps: 0383f9ff 00000000 00000000, vendor = 0
> CPU: L1 I cache: 16K, L1 D cache: 16K
> CPU: L2 cache: 128K
> Intel machine check architecture supported.
> Intel machine check reporting enabled on CPU#0.
> CPU: After vendor init, caps: 0383f9ff 00000000 00000000 00000000
> CPU:     After generic, caps: 0383f9ff 00000000 00000000 00000000
> CPU:             Common caps: 0383f9ff 00000000 00000000 00000000
> CPU: Intel Celeron (Coppermine) stepping 06
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... OK.
> Checking for popad bug... OK.
> POSIX conformance testing by UNIFIX
> mtrr: v1.40 (20010327) Richard Gooch (rgooch@xxxxxxxxxxxxx)
> mtrr: detected mtrr type: Intel
> PCI: PCI BIOS revision 2.10 entry at 0xf0e60, last bus=1
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> PCI: Using IRQ router SIS [1039/0008] at 00:01.0
> isapnp: Scanning for PnP cards...
> isapnp: No Plug & Play device found
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> Simple Boot Flag extension found and enabled.
> apm: BIOS version 1.2 Flags 0x0b (Driver version 1.14)
> Starting kswapd v1.8
> VFS: Diskquotas version dquot_6.5.0 initialized
> SGI XFS with ACLs, quota, no debug enabled
> pty: 512 Unix98 ptys configured
> Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ 
> SERIAL_PCI ISAPNP enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> Real Time Clock Driver v1.10e
> block: queued sectors max/low 71904kB/23968kB, 256 slots per queue
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz PCI bus speed for PIO modes; override with idebus=xx
> SIS5513: IDE controller on PCI bus 00 dev 01
> SIS5513: chipset revision 208
> SIS5513: not 100% native mode: will probe irqs later
> SiS630
>     ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
>     ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio
> hda: SAMSUNG SV2001H, ATA DISK drive
> hdc: WDC AC36400L, ATA DISK drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> hda: 39179952 sectors (20060 MB) w/1945KiB Cache, CHS=2438/255/63, UDMA(33)
> hdc: 12594960 sectors (6449 MB) w/256KiB Cache, CHS=13328/15/63, UDMA(33)
> Partition check:
>  hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 >
>  hdc: [PTBL] [784/255/63] hdc1 hdc2 hdc3 hdc4 < hdc5 hdc6 hdc7 hdc8 hdc9 
> hdc10 >
> floppy0: no floppy controllers found
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 8192 bind 8192)
> Linux IP multicast router 0.06 plus PIM-SM
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> XFS mounting filesystem ide0(3,2)
> XFS: WARNING: recovery required on readonly filesystem.
> XFS: write access will be enabled during mount.
> Starting XFS recovery on filesystem: ide0(3,2) (dev: 3/2)
> Ending XFS recovery on filesystem: ide0(3,2) (dev: 3/2)
> VFS: Mounted root (xfs filesystem) readonly.
> Freeing unused kernel memory: 224k freed
> Adding Swap: 265032k swap-space (priority -1)
> Adding Swap: 265032k swap-space (priority -2)
> XFS mounting filesystem ide0(3,1)
> XFS mounting filesystem ide0(3,10)
> XFS mounting filesystem ide0(3,7)
> XFS mounting filesystem ide0(3,8)
> XFS mounting filesystem ide0(3,3)
> XFS mounting filesystem ide0(3,9)
> 0x378: FIFO is 16 bytes
> 0x378: writeIntrThreshold is 16
> 0x378: readIntrThreshold is 16
> 0x378: PWord is 8 bits
> 0x378: Interrupts are ISA-Pulses
> 0x378: ECP port cfgA=0x10 cfgB=0x40
> 0x378: ECP settings irq=<none or set by other means> dma=<none or set by 
> other means>
> parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,COMPAT,ECP]
> parport0: irq 7 detected
> parport0: cpp_daisy: aa5500ff(38)
> parport0: assign_addrs: aa5500ff(38)
> parport0: cpp_daisy: aa5500ff(38)
> parport0: assign_addrs: aa5500ff(38)
> NET4: Linux IPX 0.47 for NET4.0
> IPX Portions Copyright (c) 1995 Caldera, Inc.
> IPX Portions Copyright (c) 2000, 2001 Conectiva, Inc.
> NET4: AppleTalk 0.18a for Linux NET4.0
> sis900.c: v1.07.11  4/10/2001
> PCI: Found IRQ 10 for device 00:01.1
> eth0: SiS 900 Internal MII PHY transceiver found at address 1.
> eth0: Using transceiver found at address 1 as default
> eth0: SiS 900 PCI Fast Ethernet at 0xd400, IRQ 10, 00:e0:18:06:72:a6.
> eth0: Media Link On 100mbps full-duplex
> LVM version 1.0.3(19/02/2002) module loaded
> 
> Thanks in advance for any help...
> 
> Sarwer Zafiruddin
> 
> PS - Please CC any replies to me, I am not in the list...
> 
> --------------------------
> System Administrator
> Rune Information Services
> http://www.rune.org
> e-mail:  sarwer@xxxxxxxx
> --------------------------



<Prev in Thread] Current Thread [Next in Thread>