similar to: EXT3 crash?!

(It was suggested I send a copy of this to ext3-users, so here it is - note that I need this RAID going so I've rebuilt with reiser, but would still appreciate suggestions; the message was original sent to the lkml) Hi, I've just built an 800GB RAID5 array and built an ext3 file system on it; on trying to copy data off the 200GB RAID it is replacing I'm starting to see errors of the

On Sunday March 16, gilbertd@treblig.org wrote: > Hi, > I've just built an 800GB RAID5 array and built an ext3 file system > on it; on trying to copy data off the 200GB RAID it is replacing I'm > starting to see errors of the form: > > kernel: EXT3-fs error (device md(9,2)): ext3_new_block: Allocating block in > system zone - block = 140509185 > > and >

On Monday August 4, akpm@osdl.org wrote: > Daniel Jacobowitz <dan@debian.org> wrote: > > > > I came back this morning and found: > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted >

I recently bought 2 different USB flash disks. These are some cheap no-name devices. Their parameters: bytes C/H/S ID 4194304512 509/255/63 Vendor: Generic Model: USB Flash Drive Rev: 1.00 ANSI SCSI revision: 02 4288676352 1023/132/62 Vendor: USB Model: USB 2.0 Rev: 1.00 ANSI SCSI revision: 02 When I put a FAT32 filesystem on them,

Hi, i am seeing a crash in ext3_new_block quiet often today on 2.2.19 0.0.7a fsck 1.21 ksymoops 2.3.4 on i686 2.2.19. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.19/ (default) -m /boot/System.map-2.2.19 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the

After a bit of searching through these archives I haven't found quite my problem described yet, so let me bounce this off you guys: Red Hat 7.2, I run up2date whenever patches come out; right now I'm using kernel 2.4.9-21. Things have been quite pleasant for several months, but in the last week I have begun receiving the following error messages: Feb 22 08:06:27 medmeta kernel:

Red Hat 2.2.19-6.2.12 + 0.0.7a + https://listman.redhat.com/pipermail/ext3-users/2001-November/002258.html (not tuned in /proc yet) + journal 4MB on each fs + 6 ext3 fs on raid1 (hda+hdc) + 1 ext3 fs on another disk not on raid1 (hdd) While untarring (tar zxf) a file that was on a ext3/raid1 onto hdd I got: ksymoops 2.3.4 on i686 2.2.19-6.2.12.g1. Options used -V (default) -k

Hello list I've been having the following error messages pop up in my kernel log: Apr 12 04:08:09 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: bad entry in directory #2670595: rec_len %% 4 != 0 - offset=0, inode=827218527, rec_len=20275, name_len=73 Apr 12 04:08:14 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: bad entry in directory #2670596: rec_len %% 4 != 0 -

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

On 05/01/2023 12:19, Zombie Ryushu via samba wrote: > On 1/5/23 06:22, Rowland Penny via samba wrote: >> >> >> On 05/01/2023 10:20, Zombie Ryushu via samba wrote: >>> Does anyone know how to completely remove the Computer SID of a >>> Demoted DC? As in, another DC has taken it's place, the system is >>> down and offline, but if it rejoins, it

Hi RedHat 7.2, ext3 on /, kernel 2.4.18p1. whilst updatedb was running, i had these messages appear... Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)): ext3_readdir: bad entry in directory #147553: rec_len %% 4 != 0 - offset=0, inode=1651076143, rec_len=19527, name_len=85 Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)): ext3_readdir: bad entry in directory

The handling of permissions in rsync (2.5.2) is nasty or broken. (tested platforms: Linux 2.4.x and Solaris 7) We have a directory which should only accessible to a group of users (test) : [sn@noname test]$ ls -lda /home/test drwxrws--- 2 root test 4096 Feb 13 15:44 /home/test Every user has an umask of 007 and his/her own default group: [sn@noname sn]$ id uid=500(sn)

On 1/5/23 08:10, Rowland Penny via samba wrote: > > > On 05/01/2023 12:19, Zombie Ryushu via samba wrote: >> On 1/5/23 06:22, Rowland Penny via samba wrote: >>> >>> >>> On 05/01/2023 10:20, Zombie Ryushu via samba wrote: >>>> Does anyone know how to completely remove the Computer SID of a >>>> Demoted DC? As in, another DC has

Hi all. I have two hosts with drbd: kmod-drbd83-8.3.8-1.el5.centos drbd83-8.3.8-1.el5.centos and kernel (CentOS 5.7): 2.6.18-308.4.1.el5 After a recent upgrade of kernel I have had two sitiuations when my ext3 filesystem on /dev/drbd0 became read-only. I've checked disks with smartctl -t long, they are ok. There are no messages with disks problems in /var/log/messages | dmesg. I've made

Mandrake Linux 9.0 here: I installed alsa-utils from CD1 with MCC:Software Install: in /var/log/syslog these error messages appeared (SEE BELOW): "XT3-fs error (device ide0(3,2)): ext3_new_block: Allocating block in system zone - block = 294914" Then I rebooted (because I wanted to boot in runlevel 3 to see whether I could play sound..., not relevant here). Error bootmessages appeared

Hello ext3-users, We have a RH71 machine running 2.4.16 kernel with e2fsprogs 1.25. I noticed many of these errors in our logs. EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #884828: directory entry across blocks - offset=0, inode=404600689, rec_len=23080, name_len=59 EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #966714: rec_len % 4 != 0 -

Hi ! My system is RH7.2 with Adaptec/DPT/I2O drivers (http://people.redhat.com/tcallawa/dpt/). There is a 2 disk RAID 1 array which had no disk fail. Several partition on it: Filesystem Size Used Avail Use% Mounted on /dev/sda1 1.9G 435M 1.4G 24% / /dev/sda2 13G 3.2G 9.1G 26% /home none 504M 0 503M 0% /dev/shm At this time, all

This fixes the "i_blocks went wrong when the disk filled up" problem. In ext3_new_block() we increment i_blocks early, so the quota operation can be performed outside lock_super(). But if the block allocation ends up failing, we forget to undo the allocation. This is not a serious bug, and probably does not warrant an upgrade for production machines. Its effects are: 1) errors are

Ok thanks, i make new tests. 2017-04-17 15:21 GMT-03:00 Rowland Penny <rpenny at samba.org>: > On Mon, 17 Apr 2017 14:57:45 -0300 > Luiz Guilherme Nunes Fernandes <narutospinal at gmail.com> wrote: > > > Well, i dont have sssd installed. > > OK, now we know that ;-) > > > > > With winbind i install this packages: > > yum install realmd oddjob

Can anyone give me a clue on how to find out more information from this type of error: Oct 17 05:01:08 ara kernel: EXT3-fs error (device sd(8,49)): ext3_readdir: bad entry in directory #8945865: rec_len %% 4 != 0 - offset=0, inode=93580797, rec_len=5963, name_len=106 Oct 17 05:01:08 ara kernel: EXT3-fs error (device sd(8,49)): ext3_readdir: bad entry in directory #8945869: rec_len is smaller