similar to: ext3 external journal and fstab

this has never happened to me before, and I'm somewhat at a loss. got a email from the cron thing... /etc/cron.weekly/99-raid-check: WARNING: mismatch_cnt is not 0 on /dev/md10 WARNING: mismatch_cnt is not 0 on /dev/md11 ok, md10 and md11 are each raid1's made from 2 x 72GB scsi drives, on a dell 2850 or something dual single-core 3ghz server. these two md's are in

Hello, Sorry to sound like a bad record, but I'm trying to figure out why I'm getting "Bad gzip magic numbers" errors when ISOlinux is trying to inflate the kernel. Right now I'm clueless as to what's wrong. I've tried various kernels compiled on a few different platforms. Has anyone ever seen this before? ANyone know where a better forum to ask this question

CentOS 6.3, x86_64. I have noticed when building a new software RAID-6 array on CentOS 6.3 that the mismatch_cnt grows monotonically while the array is building: # cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md11 : active raid6 sdg[5] sdf[4] sde[3] sdd[2] sdc[1] sdb[0] 3904890880 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU]

Hi, Apologies, this is going to be quite long - I'm going to provide as much info as possible. I'm running a system with ext3 fs on software RAID. The RAID set-up is as shown below: jlm@nijinsky:~$ cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid5] read_ahead 1024 sectors md0 : active raid1 hdc1[1] hda1[0] 96256 blocks [2/2] [UU] md5 : active raid1 hdk1[1] hde1[0]

Hi *, I have a problem (configuration problem probably) using the libsmbclient library (samba 2.2.6/7). I use a small c program to open directories (workgroups and servers) and list the contents of these dirs. I have two samba servers int the network. The first is everything-master and wins server, the second is nothing like that. The program works fine if I run it on the first server (using

Just to make sure somebody reacts (please) I'm forwarding this. Please cc me on replies as I'm not subscribed to this list. -------- Original Message -------- Subject: [RESEND] 2.4.20: ext3: Assertion failure in journal_forget()/Oops on another system Date: Wed, 04 Dec 2002 21:27:31 +0100 From: Andreas Steinmetz <ast@domdv.de> To: Linux Kernel Mailing List

This patch fixes an inefficiency and potential system lockup in the 2.4 kernel's ext3 filesystem. The problem has been present since 2.4.20-pre5. This patch is applicable to 2.4.20. A copy is at http://www.zip.com.au/~akpm/linux/patches/2.4/2.4.20/ext3-scheduling-storm.patch Anyone who is using tasks which have realtime scheduling policy on ext3 systems should apply this change.

Hello! I have some questions about external journals. On a 4 disk software RAID 5 I have two big devices (one 60 GB, one 180 GB). I would like to give each an external journal on a 2 disk software RAID 1 device and use data=journal. The journal will get its own partition with mke2fs -O journal_dev /dev/mdwhatever. The used 6 harddrives are all IDE drives, they are connected through

Hi All, I am trying to create an MD device. I am using the command: /sbin/mdadm --create --a /dev/md12 --level=1 --run --raid-devices=2 /dev/sda12 /dev/sdb12 to create the device, and to dynamically create the device file if needed. What I want is the device file to be created as /dev/md12, but with the -a flag it creates it as /dev/md<first unwsed minor number>. I have tried various

Hi, I'm having a problem with ext3 on my system. I'm running 2.4.13 with the appropiate ext3 patch and a software raid array with paritiions as shown below: Filesystem Size Used Avail Use% Mounted on /dev/md5 939M 237M 654M 27% / /dev/md0 91M 22M 65M 25% /boot /dev/md6 277M 8.1M 254M 4% /tmp /dev/md7 1.8G 1.3G

Hi, I'm having a problem with ext3 on my system. I'm running 2.4.13 with the appropiate ext3 patch and a software raid array with paritiions as shown below: Filesystem Size Used Avail Use% Mounted on /dev/md5 939M 237M 654M 27% / /dev/md0 91M 22M 65M 25% /boot /dev/md6 277M 8.1M 254M 4% /tmp /dev/md7 1.8G 1.3G

On Tuesday, 6 December 2016 09:46:25 CET Richard W.M. Jones wrote: > For example, converts "///usr//local//" -> "/usr/local". > --- > src/inspect-fs-unix.c | 52 +++++++++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 52 insertions(+) > > diff --git a/src/inspect-fs-unix.c b/src/inspect-fs-unix.c > index a1a757c..0fea9c8 100644 > ---

For example, converts "///usr//local//" -> "/usr/local". --- src/inspect-fs-unix.c | 52 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 52 insertions(+) diff --git a/src/inspect-fs-unix.c b/src/inspect-fs-unix.c index a1a757c..0fea9c8 100644 --- a/src/inspect-fs-unix.c +++ b/src/inspect-fs-unix.c @@ -89,6 +89,7 @@ static char *resolve_fstab_device

I am using CENTOS 5 and I am stuck where I have to repair my boot loader and all of the files are read only so I cannot fix them. How do I get around this? Thanks Chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070907/a7d2c2df/attachment.html>

//winserver/winshare /linuxdir smbfs username=username,password=password, this line doesn't work for me in fstab in CentOS 5 to mount a Windows share, it works in other versions of RH. Any Ideas? Will using Windows NFS server/client (some reading required) work better than Samba?

That seems to be the indication given by this webpage http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html However, default install of Redhat 7.2 setsup fs_passno(6th field of /etc/fstab) as 2 which asks you if you want to run fsck after an unclean shutdown The question is, is fsck required after an unclean shutdown or should one just rely on journal replay. What does fsck do when it sees an

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

[This email is either empty or too large to be displayed at this time]

/etc/fstab: //machine_name/SAN /mnt/SAN cifs defaults 0 0 [root at machine_name SAN]# mount -a Password: mount error 13 = Permission denied Problem is there is no password to the smb server. Why am I getting a password prompt when the share has full RW access and all access is granted on the share? Note, though the share is fully visable and accessable and writeable by just browsing the

Hi again, I''m trying to manage mount options in /etc/fstab with Augeas but can''t figure out how to add more than one option. augeas { "/etc/fstab": context => "/files/etc/fstab", changes => [ ''set *[file = "/tmp"]/opt nosuid'',