Emerging any version of samba results in some rather strange errors. First, I can no longer emerge any other packages. I get sandbox access violation errors (/var/cache/samba/gencache.tdb). Then if I happen to reboot, I get /dev/sda3 not found. If I boot to rescue cd and unmerge samba, this fixes the problem. Reproducible: Always Steps to Reproduce: 1. Do a fresh gentoo install (gentoo-sources 2.6.12-r10) 2. Setup LDAP client config (using same system-auth) 3. Install Samba...crash and burn. Actual Results: Can not long emerge software. Sandbox access violation errors. This one is way beyond me, but the only thing I may have different fromt he rest of the world is LDAP authentication. No TLS, jsut plain LDAP. I have done two clean installs testing this and it happens every time. Hardware: New Dell precision 470 (64-bit) Running 32-bit gentoo. SATA Drives Intel E7525 Chip
Sorry, we can't really guess; emerge --info missing, samba version missing, any actual error messages missing as well. Reopen with relevant information. Thanks.
(In reply to comment #1) > Sorry, we can't really guess; emerge --info missing, samba version missing, any > actual error messages missing as well. Reopen with relevant information. Thanks. emerge --info Portage 2.0.51.22-r2 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r1, 2.6.12-gentoo-r10 i686) ================================================================= System uname: 2.6.12-gentoo-r10 i686 Intel(R) Xeon(TM) CPU 3.00GHz Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5-r2 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown / usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=i686" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.osuosl.org/ http://distro.ibiblio.org/pub/linux/distributions/gentoo/ ftp://gento o.chem.wisc.edu/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa apm arts avi berkdb bitmap-fonts browserplugin cdr crypt cups curl dvd eds emboss encode esd fa m flac foomaticdb fortran gdbm gif gpm gstreamer gtk2 imlib ipv6 java jpeg kde ldap libg++ libwww live mad mikm od mmx motif mp3 mpeg ncurses nls nvidia ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime readl ine real sdl spell sse sse2 ssl tcpd theora tiff truetype truetype-fonts type1-fonts vorbis win32codecs winbind xanim xinerama xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY Samba Version [ebuild N ] net-fs/samba-3.0.14a-r2 -acl +cups -doc -kerberos +ldap -libclamav -mysql -oav +pam -postgres +python -quotas +readline (-selinux) +winbind -xml +xml2 0 kB Errors: On boot: /dev/sda3 (root partition) not found bad. Bad superblock etc... I have duplicated this a third time now however now I'm not getting emerge sandbox errors. I think it was due to an "emerge system" today. I still cannot boot after emerging samba. Current fix: boot using 2005.1 univeral, chroot to os and "emerge -C samba".
if it's not due to broken fs (/sbin/fsck.* ...), then the emerge errors may be caused by sandbox version: sys-apps/sandbox stable version for your arch is 1.2.12 Anyway, this shouldn't affect your boot sequence: I personally use every combination of diskless, ldap, and a lot of other use flags. What are the errors at boot (console boot output)? Is samba enabled by default ('rc-update show')?
(In reply to comment #3) > if it's not due to broken fs (/sbin/fsck.* ...), then the emerge errors may be > caused by sandbox version: sys-apps/sandbox stable version for your arch is 1.2.12 > > Anyway, this shouldn't affect your boot sequence: I personally use every > combination of diskless, ldap, and a lot of other use flags. What are the errors > at boot (console boot output)? Is samba enabled by default ('rc-update show')? There error do appears to be broken fs. I'm getting fsck.ext3: file not found...then onto bad superblock messages. Sorry I don't know how to cut and paste from boot sequence or I would. I'll update sandbox and try emerging samba again. Then try and boot: first with samba disabled then enabled and see what happens. Stay tuned.
(In reply to comment #3) I updated sandbox and emerged samba without adding it to the the default boot and I immediatly got the error. I wrote down the specifics this time: fsck.ext2: No such file or directory while trying to open /dev/sda3 /dev/sda3: The superblock could not be read.
closing, since this is not due to a samba bug. Should you need further info for your data recovery, look at the last posts of http://forums.gentoo.org/viewtopic-t-195220.html
(In reply to comment #6) > closing, since this is not due to a samba bug. > Should you need further info for your data recovery, look at the last posts of > http://forums.gentoo.org/viewtopic-t-195220.html Perhaps I have not made the problem clear. There is "No" data loss. Simply installing Samba causes the system to be unbootable. Doing an "emerge -C samba" resolves the boot problem, but I still an unble to have samba installed. This makes me think it is directly related to the samba install.
Well, samba is only a userspace tool, albeit with strong kernel connections. It _can't_ cause broken fs/bad superblock errors, nor render a machine unbootable, considered also that in some of your cases samba is not included in the default active services. Changes are that your fs is corrupted/invalid, and samba simply (in its activity, for the simple occupation of some blocks in the hard drive, or the call of a segment of the inode table that is unrealiable) causes the system to warn you of this bad condition. The boot sequence is designed to stop itself, before doing more harm: thus the unbootable machine. It is never a good idea to trust a broken fs: you've been lucky to not loose any data, but the better thing to do now is to resolve the error, or to transfer your datas on a more secure place (==partition, or network mount). Only once this is done, you could try installing samba in this new location. Again, this is not related to samba. I'm leaving this bug open for a while for news, but bugzilla is not the proper location for these issues: unless you can show how to replicate this condition from a proven stable situation, I suggest you to try the forums, expecially the url in comment #6.
(In reply to comment #8) > Well, samba is only a userspace tool, albeit with strong kernel connections. It > _can't_ cause broken fs/bad superblock errors, nor render a machine unbootable, > considered also that in some of your cases samba is not included in the default > active services. > Changes are that your fs is corrupted/invalid, and samba simply (in its > activity, for the simple occupation of some blocks in the hard drive, or the > call of a segment of the inode table that is unrealiable) causes the system to > warn you of this bad condition. The boot sequence is designed to stop itself, > before doing more harm: thus the unbootable machine. I agree, everything you are saying makes perfect sense. However, since the last time i installed Samba I have installed roughly 4.5 gigs of additional software and run fsck many times. I just installed samba again and got the same errors so I ran fsck from the univeral disk in the broken state. Here are the results: livecd root # fsck.ext3 -f /dev/sda3 e2fsck 1.37 (21-Mar-2005) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/sda3: 298693/8142848 files (1.7% non-contiguous), 4216325/16279869 blocks Good FS! I think we are missing something, but at the risk of being a pain in the ass I'm going to say close this. This is a very new smp machine machine (Dell Precision 470 - Supposedly redhat certified) and I think there may be a kernel issue lurking. I'm going to try and take the kernel approach. My only fear is that they may be a lot of people getting this error and never know it might be tied to a samba install. It took me three days, two ground up installs and two hard drives to figure out the boot problem only happened after samba was installed. I'll also try and create a duplicate machine in vmware if I get time and se how that goes. Thanks for all your help.
No news, so closing. If there are still issues, please let me know
