Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 95846 - Plausible fstab value causes filesystem corruption
Summary: Plausible fstab value causes filesystem corruption
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-12 03:14 UTC by Kevin Bowling
Modified: 2005-08-17 21:06 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Bowling 2005-06-12 03:14:08 UTC
If the sixth field of the fstab is set to '1' for more than one mount, bad
things happen on boot.  No warning of this is placed in the default fstab.

Example--

# <fs>                  <mountpoint>    <type>          <opts>                 
<dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/sda2               /boot           ext3            noatime                 0 1
/dev/sda4               /               ext3            noatime                 0 1


Reproducible: Always
Steps to Reproduce:
1. Have '1' in the sixth field of /etc/fstab for two mounts

Actual Results:  
Filesystem corruption on boot checks, end result root mounted RO further
complicating things.

Expected Results:  
Warning placed in default fstab, or not corrupt filesystem?

c360-hppa ~ # emerge info
Portage 2.0.51.19 (default-linux/hppa/2005.0, gcc-3.3.5,
glibc-2.3.4.20040808-r1, 2.6.11-pa2 parisc)
=================================================================
System uname: 2.6.11-pa2 parisc PA8500 (PCX-W)
Gentoo Base System version 1.6.12
Python:              dev-lang/python-2.3.5 [2.3.5 (#1, Jun 11 2005, 14:28:16)]
dev-lang/python:     2.3.5
sys-apps/sandbox:    [Not Present]
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.9.5, 1.5, 1.8.5-r3, 1.6.3, 1.7.9-r1, 1.4_p6
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.16
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="hppa"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=2.0 -fomit-frame-pointer -pipe -mschedule=8000"
CHOST="hppa2.0-unknown-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O1 -fomit-frame-pointer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="hppa X apache2 berkdb bitmap-fonts crypt cups curl dga directfb fbcon
foomaticdb fortran ftp gd gdbm gif gpm imap imlib innodb ipv6 jpeg kde ldap
libwww mysql mysqli ncurses nls pam pcntl pcre perl php pic png python readline
samba sockets spell spl ssl svg tcpd truetype truetype-fonts type1-fonts
userlocales xml2 zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Comment 1 SpanKY gentoo-dev 2005-06-12 13:25:05 UTC
could you show us what you're seeing at boot time ?  the 6th field controls how
filesystems are checked in parallel and shouldnt matter if you have many in the
same level
Comment 2 Kevin Bowling 2005-06-12 15:11:07 UTC
I guess 1 may only be used on a single filesystem, the root.  I think the real
damage was done after it continued booting in a quasi-readonly state.  The
system is working now after I changed sda2 to 2 and ran fsck to clean up the
mess on sda4.

dmesg:

(none) / # dmesg
Linux version 2.6.11-pa2 (root@livecd) (gcc version 3.3.5 (Gentoo 3.3.5-r1,
pie-8.7.7.1)) #1 Sun Jun 12 05
FP[0] enabled: Rev 1 Model 16
The 32-bit Kernel has started...
Determining PDC firmware type: System Map.
model 00005c60 00000481 00000000 00000002 781120ae 100000f0 00000008 000000b2
000000b2
vers  00000100
CPUID vers 14 rev 0 (0x000001c0)
capabilities 0x2
model 9000/785/C360
Total Memory: 1024 Mb
On node 0 totalpages: 262144
  DMA zone: 262144 pages, LIFO batch:16
  Normal zone: 0 pages, LIFO batch:1
  HighMem zone: 0 pages, LIFO batch:1
LED display at 4028170241 registered
Built 1 zonelists
Kernel command line: root=/dev/sda4 console=ttyS0 palo_kernel=2/vmlinux
PID hash table entries: 4096 (order: 12, 65536 bytes)
Console: colour dummy device 160x64
Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 131072 (order: 7, 524288 bytes)
Memory: 1048576k available
Calibrating delay loop... 729.08 BogoMIPS (lpj=364544)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
NET: Registered protocol family 16
Searching for devices...
Found devices:
1. U2-IOA BC Runway Port at 0xfff88000 [8] { 12, 0xf, 0x580, 0x0000b }
2. Dino PCI Bridge at 0xf2000000 [8/0] { 13, 0x3, 0x680, 0x0000a },  additional
addresses: 0xf2800000 0xf
3. Raven U/L2 Dino RS-232 at 0xf2003000 [8/0/63] { 10, 0x0, 0x006, 0x0008c }
4. Raven+ w SE FWSCSI Core BA at 0xffd00000 [8/16] { 11, 0x0, 0x056, 0x00081 },
 additional addresses: 0x
5. Raven+ w SE FWSCSI Core RS-232 at 0xffd05000 [8/16/4] { 10, 0x0, 0x056, 0x0008c }
6. Raven+ w SE FWSCSI Core SCSI at 0xffd06000 [8/16/5] { 10, 0x0, 0x056, 0x00082 }
7. Raven+ w SE FWSCSI Core Centronics at 0xffd02000 [8/16/0] { 10, 0x0, 0x056,
0x00074 },  additional add
8. Raven+ w SE FWSCSI Core Audio at 0xffd04000 [8/16/1] { 10, 0x4, 0x056, 0x0007b }
9. Raven+ w SE FWSCSI Core PS/2 Port at 0xffd08000 [8/16/7] { 10, 0x0, 0x056,
0x00084 }
10. Raven+ w SE FWSCSI Core PS/2 Port at 0xffd08100 [8/16/8] { 10, 0x0, 0x056,
0x00084 }
11. U2-IOA BC GSC+ Port at 0xf203f000 [8/63] { 7, 0x1, 0x501, 0x0000c }
12. Raven U/L2 Dino PS/2 Port at 0xf2001000 [8/1] { 10, 0x0, 0x006, 0x00096 }
13. U2-IOA BC Runway Port at 0xfff8a000 [10] { 12, 0xf, 0x580, 0x0000b }
14. U2-IOA BC GSC+ Port at 0xf103f000 [10/63] { 7, 0x1, 0x501, 0x0000c }
15. Cujo PCI Bridge at 0xf1000000 [10/0] { 13, 0x1, 0x682, 0x0000a }
16. Dino RS-232 at 0xf1003000 [10/3] { 10, 0x0, 0x007, 0x0008c }
17. Raven W 360 (9000/780) at 0xfffa0000 [32] { 0, 0x0, 0x5c6, 0x00004 }
18. Memory at 0xfffb1000 [49] { 1, 0x0, 0x097, 0x00009 }
CPU(s): 1 x PA8500 (PCX-W) at 367.111100 MHz
Whole cache flush 601449 cycles, flushing 272966636 bytes 110164392 cycles
Setting cache flush threshold to 40 (1 CPUs online)
Found U2 at 0xfff88000
Found U2 at 0xfff8a000
Lasi version 0 at 0xffd00000 found.
Dino version 3.1 found at 0xf2000000
Cujo version 2.0 found at 0xf1000000
Enabling Cujo 2.0 bug workaround
Cujo: No PCI devices enabled.
SCSI subsystem initialized
unwind_init: start = 0x1033a130, end = 0x1035c4b0, entries = 8760
Initializing Cryptographic API
Soft power switch enabled, polling @ 0xf0140000.
STI GSC/PCI core graphics driver Version 0.9a
STI PCI graphic ROM found at f2f80000 (64 kB), fb at f6000000 (32 MB)
    id 2d08c0a7-9a02587, conforms to spec rev. 8.0a
    graphics card name: PCI_GRAFFITIDX1280
sticon: Initializing STI text console.
Console: switching to colour STI console 160x64
Console: switching to colour frame buffer device 160x64
fb0: stifb 1280x1024-8 frame buffer device, PCI_GRAFFITIDX1280, id: 2d08c0a7,
mmio: 0xf6100000
lp: driver loaded but no devices found
Generic RTC Driver v1.07
serio: GSC PS/2 keyboard port at 0xffd08000 irq 20 @ 8:16:7
serio: GSC PS/2 mouse port at 0xffd08100 irq 20 @ 8:16:8
HP SDC: No SDC found.
HP SDC MLC: Registering the System Domain Controller's HIL MLC.
HP SDC MLC: Request for raw HIL ISR hook denied
Serial: 8250/16550 driver $Revision: 1.90 $ 13 ports, IRQ sharing enabled
ttyS0 at MMIO 0xffd05800 (irq = 16) is a 16550A
ttyS1 at MMIO 0xf2003800 (irq = 21) is a 16550A
parport_init_chip: initialize bidirectional-mode.
parport0: PC-style at 0xffd02800, irq 18 [PCSPP,TRISTATE]
lp0: using parport0 (interrupt-driven).
io scheduler noop registered
io scheduler anticipatory registered
loop: loaded (max 8 devices)
Linux Tulip driver version 1.1.13 (December 15, 2004)
tulip0: no phy info, aborting mtable build
tulip0:  MII transceiver #1 config 1000 status 782d advertising 0061.
eth0: Digital DS21143 Tulip rev 48 at 80000080, 00:60:B0:EA:C8:BD, IRQ 24.
sym0: <875> rev 0x4 at pci 0000:00:13.0 irq 23
sym0: No NVRAM, ID 7, Fast-20, SE, parity checking
sym0: SCSI BUS has been reset.
scsi0 : sym-2.2.0
 target0:0:0: FAST-20 WIDE SCSI 40.0 MB/s ST (50 ns, offset 15)
scsi scan: 255 byte inquiry failed.  Consider BLIST_INQUIRY_36 for this device
  Vendor: COMPAQ    Model: WDE9100S          Rev: 1.35
  Type:   Direct-Access                      ANSI SCSI revision: 02
 target0:0:0: tagged command queuing enabled, command queue depth 16.
 target0:0:0: Beginning Domain Validation
 target0:0:0: asynchronous.
 target0:0:0: wide asynchronous.
 target0:0:0: Domain Validation skipping write tests
 target0:0:0: FAST-20 WIDE SCSI 40.0 MB/s ST (50 ns, offset 15)
 target0:0:0: Ending Domain Validation
53c700: Version 2.8 By James.Bottomley@HansenPartnership.com
scsi1: 53c710 rev 2
scsi1 : LASI SCSI 53c700
  Vendor: TOSHIBA   Model: CD-ROM XM-5701TA  Rev: 1557
  Type:   CD-ROM                             ANSI SCSI revision: 02
 target1:0:2: Beginning Domain Validation
 target1:0:2: asynchronous.
 target1:0:2: Domain Validation skipping write tests
 target1:0:2: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 8)
 target1:0:2: Ending Domain Validation
st: Version 20041025, fixed bufsize 32768, s/g segs 256
SCSI device sda: 17773500 512-byte hdwr sectors (9100 MB)
SCSI device sda: drive cache: write through
SCSI device sda: 17773500 512-byte hdwr sectors (9100 MB)
SCSI device sda: drive cache: write through
 sda: sda1 sda2 sda3 sda4
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
sr0: scsi-1 drive
Uniform CD-ROM driver Revision: 3.20
Attached scsi CD-ROM sr0 at scsi1, channel 0, id 2, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0
Attached scsi generic sg1 at scsi1, channel 0, id 2, lun 0,  type 5
mice: PS/2 mouse device common for all mice
gscps2.c: timeout - could not write byte 0xed
gscps2.c: sending byte 0xed failed.
gscps2.c: timeout - could not write byte 0xed
gscps2.c: sending byte 0xed failed.
Advanced Linux Sound Architecture Driver Version 1.0.8 (Thu Jan 13 09:39:32 2005
UTC).
ALSA device list:
  #0: Harmony at 0xffd04000, irq 19
NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning (device sda4): ext3_clear_journal_err: Filesystem error recorded
from previous mount: IO e
EXT3-fs warning (device sda4): ext3_clear_journal_err: Marking fs in need of
filesystem check.
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 440k freed
Adding 749560k swap on /dev/sda3.  Priority:-1 extents:1
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2005-06-12 15:59:02 UTC
(In reply to comment #2)
> I guess 1 may only be used on a single filesystem, the root.  

Yup. From man fstab:

The root filesystem should be specified with a fs_passno of 1, and other
filesystems should have a fs_passno of 2. 

Despite this, one should use 0 0 with reiserfs, at least per
http://www.namesys.com/faq.html#fstab ;-)

Comment 4 SpanKY gentoo-dev 2005-08-17 21:06:45 UTC
added a note to default fstab about using '1' only for the root filesystem