similar to: reproducible ext3 corruption with sync option, 2.4.17, images available

(sort-of xposted from linux-kernel) Hi, I am wondering how to interpret this error message, which popped up on a 2.4.26 SMP x86 box two days ago: EXT2-fs: corrupt root inode, run e2fsck init_special_inode: bogus imode (37316) EXT2-fs: corrupt root inode, run e2fsck init_special_inode: bogus imode (37316) EXT2-fs: corrupt root inode, run e2fsck The problem is, the error message doesn't

I've been thinking of making a (mostly) solid-state asterisk pbx. Take either centos or some other distro, cut it down to bare minimum and put asterisk + AMP on. Something that could be put onto a usb2.0 flash stick, bootable. Modern flash devices (usb, compactflash) have builtin wear leveling management and will last longer than you think:

Hello Luis Thansk Yes we tried that and it works, but if you are in the field and only have new clean compact-flash and no DOS, you are in trouble. I can syslinux directly to the USB card-reader/writer under Linux without problems too. It just appears as a SCSI-device(/dev/sda). best regards ole at danelec.dk * danelec electronics a/s * Blokken 44 * DK-3460 Birkeroed * DENMARK *

I have several CentOS5 hosts in a VMware ESX 3.5.0 226117 environment using iSCSI storage. Recently we've begun to experience journal aborts resulting in remounted-read-only filesystems as well as other filesystem issues - I can unmount a filesystem and force a check with "fsck -f" and occasionally find errors. I've found -

Hello I think syslinux is great and just downloaded 2.00 and will start using it in a couple of days. 1. We use an IDE<->compactflash-adapter in our target-system. We use a USB-compact-flash reader/writer(SanDisk/ImageMate) on our linux-host to write the flash. It appears in the Linux-system as '/dev/sda', and we can use syslinux and mount for copying kernel, syslinux.cfg and our

Hi, I'm running kernel 2.6.8-15, lvm2 v2.01.04-5 and acl v2.2.23-1 on a Sunblade 100 (sparc). In a few months we have experienced for several times that an ext3 filesystem is remounted as read-only (this is due to the option "errors=remount-ro" in /etc/fstab). Sometimes there is no error in log files but sometimes we see: kernel: init_special_inode: bogus i_mode (3016) kernel:

Hey, I've a problem with an ext3 filesystem and don't know how to fix it or find the failure :( The Hardware: Tyan mainboard, AMD Athlon CPU, ARECA ARC-1120 RaidController Raid5 with 400GB Seagate HD's, 756 MB Ram, other harddisks for system, network and avm isdn controller. Couse of the filesystem problems I run memtest and found one bad memory module which I replaced yet. The

Hello, I am doing some testing on a PXA270 based processor (on a single board computer) which makes the processor vulnerable to bit flips. One such bit flips seems to have corrupted the file system. The debug port on the board (it is a single board computer) had the following message when i think the FS corruption occured : <7>init_special_inode: bogus i_mode (33061) init_special_inode:

The difference between kdev_t and dev_t in 2.4 is rather theoretical, no need to clutter up the source for it. Index: src/inode.c =================================================================== --- src/inode.c (revision 969) +++ src/inode.c (working copy) @@ -1877,11 +1872,8 @@ case OCFS_ATTRIB_FIFO: case OCFS_ATTRIB_SOCKET: { -#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)

I've just updated to a snapshot of 4.9-PRERELEASE. The usb/umass support seems *much* more stable than I found it with 4.8. My Oracom USB MP3 player now works without errors, and achieves up to 400KB/sec throughput. However, if I connect my Belkin CompactFlash reader instead, that's very, very slow indeed. The greatest data rate I see is about 4KB/sec, although no errors are

Hello! I'm using a CompactFlash as storage device. Since those CF cards only have limited write cycles (CF does wear-levelling by itself, but you don't want to write too many timet so the card) i was wondering by what a factor the journaling of ext3 increases the write accesses to the CompactFlash compared to ext2. Thanks a lot already for your help! Sincerely Chris Braun

Hi folks, I'm trying to make a CompactFlash bootable with SYSLINUX. The hard part is that I'm trying to run SYSLINUX on Windows 2000 and am attempting to write to the compactflash that's plugged in via a USB reader/writer. Its not working -- Windows complains about the 16-bit subsystem wanting direct access to the drive. So then is the problem SYSLINUX fighting with Windows or

SYSLINUX 2.10 2004-06-18 That is all I get when I boot my system off a CompactFlash card in an IDE adapter, no matter how long I wait. What debugging steps are recommended? I'm willing to get down and dirty with assembler, and I'd appreciate suggestions of what to suspect and where to start. Details: This is a Crucial 128MB CompactFlash card in a non-hot-swap CF-IDE adapter which

Hi folks, I hit the syslinux homepage for the first time in a while. The stuff just works, so there's no reason to come to the website, eh? :) Anyway, the first line is "The SYSLINUX Project covers lightweight bootloaders for floppy media (SYSLINUX)", and I think that this needs to be expanded a bit. I use SYSLINUX on CompactFlash, and it works great because together with

Hi all- I'm trying to use a SanDisk Cruzer Micro flash drive (usb, 512MB). It has CruzerLock version 2.0 Security software in it. When I plug it in, it is recognized OK. When I open the drive, I have a file to open: CruzerLock2.exe. It has the Wine icon. But when I click on it, I get: CLZ1020: cannot locate the application in it's required location:

Hello, I have a question about ext3 write activity. I am considering using an ext3 fs on a CompactFlash disk for my data-logging application (power can disapear anytime). The quantity & frequency of the data logged itself is not a problem at all considering flash wear. But I'm a bit worried about the kernel/ext3 doing regular writes by itself even when there are no userspace writes.

Pam_SMB allows Linux clients to validate their passwords against an NT PDC, so the only thing you have to do is set up the accounts on the Linux side with an '*' in the /etc/passwd entry. This can be done using a list of users: #!/bin/bash for i in `cat myuserlist`; do /usr/sbin/adduser -p '*' $i with various other command line options, such as "-s

I'm getting a strange error pop up on my box: ############################# No more mirrors are available Required data could not be found on any of the configured software sources. There were no more download mirrors that could be tried. More details failure: repodata/filelists.sqlite.bz2 from elrepo: [Errno 256] No more mirrors to try. ############################# How to figure out

I have a Pentium 4 machine that does not boot from my 32GB SanDisk Cruzer. Its first partition is 24GB and FAT32, to serve as cross-platform storage. There is a second partition of 7GB in EXT2 which is bootable and contains a Linux system armed with syslinux (extlinux). This works fine booting off of recent laptops and desktops alike. This particular desktop has in its BIOS everything related to

I may have asked about this before, but I can't find any records of so doing in my saved mail (which includes almost everything I ever read or write): All of a sudden, I am not getting flash drives automatically mounted in CentOS 5.3 with GNOME - they are recognized by the hardware, but there seems to be a (new?) problem with the maps. Here's the tail end of dmesg: usb 1-10: new high