similar to: Confusing -t for -T causes bad block count error

>Yes, if you are creating larger files. By default e2fsck assumes the average >file size is 8kB and allocates a corresponding number of inodes there. If, >for example, you are storing lots of larger files there (digital photos, MP3s, >etc) that are in the MB range you can use "-t largefile" or "-t largefile4" >to specify an average file size of 1MB or 4MB

I need to get around the requirement of --exclude=* to have all the parent directories of the files and directories that are to be included. So given the file.. /startdirectory/subdirectory1/subdirectory2/filetobecopied I need to include / /subdirectory1 /subdirectory1/subdirectory2 I could just include the entire directory structure , but alternatively just include the needed paths. So the

Recently, our backup software oddly decided to rebackup a good portion of our file server instead of just doing an incremental. When I examined various sets of presumably identical files, I discovered that the modification dates on these files were no longer the same. Many files were re-dated to exactly one hour later such that if a file had been modified on 3/24/04 at 2:24:53 PM, it's

I created a filesystem as follows: mke2fs -j -O dir_index -O sparse_super -T largefile /dev/drbd/6 Here's the the output from df Filesystem Size Used Avail Use% /dev/drbd/6 475G 33M 452G 1% It seems that ext3 has taken 23 GB, which is about 5% of the total disk size, for itself. Is that right? If that is, indeed, the case, why does df just list 33M as being

I made a filesystem (mke2fs -j) on a logical volume under kernel 2.6.20 on a 64-bit based system, and when I try to mount it, ext3 complains with EXT3-fs: dm-1: couldn't mount because of unsupported optional features (80). I first thought I just forgot to make the filesystem, so I remade it and the error is still present. I ran fsck on this freshly made filesystem, and it completed with

I have two Opteron-based Tyan systems being supported by PCI-e Areca cards. There is definitely an issue going on in the two systems that is causing significantly degraded performance of these cards. It appeared, initially, that the SATA backplane on the Tyan chassis was wholly to blame. But then I made an odd discovery. I'm running from the Ubuntu LiveCD for 64-bit. It uses kernel

If I login to our Samba box (RedHat 7.1 + 2.4.20) under Windows 2K via Start->Run->share name, I get logged in almost immediately. It averages about 25 seconds under XP. This behavior has been true in various versions of Samba since I believe XP was available and is reproducible on every (several) Windows 2K/XP boxes I have tried. This is a workgroup environment with Samba acting as

This mib used to work, so is there a way to go back to the version prior to this one without downgrading the whole package? * Starting UPS drivers... Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Generic SNMP UPS driver 0.44 (2.4.1) Detected GXT2-2000RT120 on host upswallleft (mib: ietf 1.3) [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.4.4.1.4.0: Error in

I have had in years past seen hardware (SCSI) RAID controllers lose it electronically causing the kernel to fill the logs with scary SCSI messages and ext3 to complain about "holes" in the filesystem like so: Sep 7 14:47:17 thewarehouse1 kernel: EXT3-fs error (device sd(8,81)): ext3_readdir: directory #376833 contains a hole at offset 0 I'm using drbd and heartbeat so whatever

Compiling e2fsprogs-1.35 under Linux complains.... make[2]: Entering directory `/src/kernel/e2fsprogs-1.35/po' : --update cs.po e2fsprogs.pot rm -f cs.gmo && : -c --statistics -o cs.gmo cs.po mv: cannot stat `t-cs.gmo': No such file or directory make[2]: *** [cs.gmo] Error 1 make[2]: Leaving directory `/src/kernel/e2fsprogs-1.35/po' make[1]: *** [all-progs-recursive] Error 1

Dual Opteron system running ext3 atop drbd (network RAID) devices, which, in turn, are atop LVM logical volumes. The underlying device is hardware SCSI RAID via a LSILogic HBA. The kernel is vanilla 2.6.13 on a Gentoo-based system. A panic occurred, which contains references to ext3 code. I'm not sure how others manage to get these typed out, but I'm manually typing it from

drbd-0.7.19 under kernel 2.6.17-rc4 is running on a primary node standalone. There are 8 resources in the same group. fsck.ext3 -fv is being run simultaneously on all of them. Each of the drbd devices are running on an lv, which all belong to a single pv. The actual "disk" is a hardware RAID connected via SCSI (i.e., the mpt driver). Five of the fsck finished their tasks

For some odd reason, fsck has suddenly become confused about what "auto" means after I changed the root to ext3 and everything in fstab to auto. This is happening on a Redhat Pentium III box running 2.4.9 and I also installed just recently util-linux 2.11l and glibc 2.2.4. fsck is 1.2.5 as indicated below. fsck 1.25 (20-Sep-2001) Checking all file systems. Could not determine

I am trying various config files to get some kind of guest start and they all seem to get stuck with the error, Error: Device 768 (vbd) could not be connected. Hotplug scripts not working. xen is 3.3.1 and Dom0 is 2.6.29. Here''s an example of one such config that reproduces this error. kernel = "/usr/lib/xen/boot/hvmloader" builder = ''hvm'' device_model =

I am working with three Liebert GXT2 UPSes connected via local TCP/IP under Linux 2.6.25.1 and getting a series of messages. First, at start, the drivers complains that the Liebert apparently extract information from certain MIBs in the ietf MIB file.... Network UPS Tools - UPS driver controller 2.2.2 Network UPS Tools - Multi-MIBS SNMP UPS driver 0.421 (2.2.2) Warning: This is an experimental

drbd-0.7.19 under kernel 2.6.17-rc4 is running on a primary node standalone. There are 8 resources in the same group. fsck.ext3 -fv is being run simultaneously on all of them. Each of the drbd devices are running on an lv, which all belong to a single pv. The actual "disk" is a hardware RAID connected via SCSI (i.e., the mpt driver). Five of the fsck finished their tasks

drbd-0.7.19 under kernel 2.6.17-rc4 is running on a primary node standalone. There are 8 resources in the same group. fsck.ext3 -fv is being run simultaneously on all of them. Each of the drbd devices are running on an lv, which all belong to a single pv. The actual "disk" is a hardware RAID connected via SCSI (i.e., the mpt driver). Five of the fsck finished their tasks

Here it is: [2005/06/20 05:27:08, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(353) find_domain_master_name_query_fail: Unable to find the Domain Master Browser name KENNEDY<1b> for the workgroup KENNEDY. Unable to sync browse lists in this workgroup. I scanned through previous postings. This is one of those messages that Samba throws up apparently for no good

A PC running Windows 95 has a share mounted from a Samba 2.0.7 server running under Mac OS X Server. An attempt is being made to copy a file on the PC called suse.iso to a subdirectory of the share (faberlab) on the Samba server. The PC hangs a bit and eventually complains that it can't create the file. Here is the debug log starting from the moment the copy has begun... [2000/06/02

Box with Redhat 7.1 and kernel 2.4.20 has a hardware RAID (about 750 gigs data) attached via an Adaptec 29160 LP card... I began seeing numerous SCSI errors in my logs for our external hardware RAID and input/output errors on test attempts to copy files via cp. Rebooted and immediately saw the errors as the disk was initially accessed by the Adaptec driver. The RAID controller did not