Displaying 20 results from an estimated 300 matches similar to: "How to interpret corruption error message"
2005 Nov 03
1
filesystem remounted as read only
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:
2006 Dec 27
5
Problem with ext3 filesystem
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
2002 Mar 18
0
reproducible ext3 corruption with sync option, 2.4.17, images available
I have been using ext3 filesystem from 2.4.17 kernel in the default
"ordered" mode on an 64 MB SanDisk compactflash. The disk itself was used on
NationalGeode embedded board.
The following entry was used in fstab (I know, may be stupid, but should not
crash the filesystem?)
/dev/hda1 / ext2 defaults,sync 1 1
After the board is switched off, it does not boot
2001 Oct 28
4
Extended Attributes and Access Control Lists
Hello,
I have today released an initial version of extended attributes and access
control lists for ext3 (patch against the 2.4.13-ac3 kernel). Eric Jarman
<ejarman@acm.org> has contributed a lot to this effort.
Since I'm not very much into the innards of ext3, can some of you please
take a look at the patch, and see whether it contains any flaws (and tell
me which flaws)? Thanks!
The
2011 Feb 13
2
Journal Aborts in VMware ESX (Filesystem Corruption)
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 -
2007 Mar 28
2
ssl with openwrt OS
Hi.
I'm still facing troubles on my way. This time concerning ssl encryption.
only dovecot-auth starts...
imap and pop3 go down with this log
dovecot: Mar 23 18:34:19 Info: Dovecot v1.0.rc27 starting up
dovecot: Mar 23 18:34:20 Error: Temporary failure in creating login processes, slowing down for now
dovecot: Mar 23 18:34:20 Error: imap-login: Can't load certificate file
2005 Oct 31
2
What is the history of CONFIG_EXT{2,3}_CHECK?
Can anyone tell me the history of CONFIG_EXT{2,3}_CHECK?
There is code for a "check" option for mount if these options are
enabled, but there's no way to enable them.
TIA
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
2006 Oct 25
1
FS corruption? bogus i_mode
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:
2004 Jun 02
0
[PATCH] kill 2.4 dev_t vs kdev_t crap
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)
2006 May 26
1
[PATCH - 2.6.17-rc5] ext3: Fix missed mutex unlock - unroll
Hi,
I believe the following patch in the GIT - 2.6.17-rc5 is not correct:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=75616cf9854b83eb83a968b1338ae0ee11c9673c
It is the second of the two patches contributed by Leonid Ananiev. This
one incorrectly adds the super block unlocking in the error path, though.
As we can see in the function ext3_group_add() the
2014 Feb 13
3
Libguestfs (1.22.6) driver/changes for mingw/win32
Hi,
I attached the changes I made to a vanilla libguestfs-1.22.6 in order to
make it work in mingw/win32.
Added is also the patch required to make QEMU compatible (add a command to
QMP that lists the supported devices (the regilat way you do it print it to
stderr, which is difficult to redirect in win32)).
This is done on behalf of Intel Corp.
Thanks,
Or (oberon in irc)
2007 Jul 14
1
Kernel panic in ext3:dx_probe, help needed
This may or may not be ext3 related but I am trying to find any pointers
which might help me. I got a number of HP Proliant DL380 g5 with a P400
controller and also two qla2400 cards. The OS is RedHat EL4 U5 x86_64.
Every time during reboot these systems panic after the last umount and I
believe before the cciss driver is getting unloaded. The last messages I
am able to see are:
md: stopping
2009 Apr 02
1
problem with svyglm()
Hello,
I'm trying to use the function svyglm in the library survey.
I create a data survey object:
data_svy<- svydesign(id=~PSU, strata=~sample_domain,
weights=~sample_weight, data=data, nest=TRUE)
and I try to use svyglm() with little success:
R<-svyglm(data_svy[,4]~(data_svy[,iCol]==listModality[[iVar]]
[iMod]),design=data_svy, family=binomial(link="logit")
Error in
2013 Nov 23
0
[Bioc-devel] package citations
(xposted to bioc-devel and r-devel as I feel it is relevant to both
communities)
As someone whose body of work is likely to consist mostly of
infrastructural packages and research directly in computing I
wholeheartedly agree with Kasper's suggestion that we as a community should
work to provide and use package citations. I borrow heavily from existing
work in terms of both concept and
2007 Jun 29
2
Mknod: Operation not permitted
When trying to move my root to a btrfs filesystem, I found a missing
feature (or a bug). It's not possible to create device files. To
reproduce, run this on a btrfs filesystem:
mknod test c 1 1
result:
mknod: `test': Operation not permitted
Frank
2007 Mar 23
0
ssl on embedded device
Hi.
I'm still facing troubles on my way. This time concerning ssl encryption.
only dovecot-auth starts...
imap and pop3 go down with this log
dovecot: Mar 23 18:34:19 Info: Dovecot v1.0.rc27 starting up
dovecot: Mar 23 18:34:20 Error: Temporary failure in creating login processes, slowing down for now
dovecot: Mar 23 18:34:20 Error: imap-login: Can't load certificate file
2002 May 13
5
Assertion failure in do_get_write_access() at transaction.c:609:
Hi all (and developers in particular)
I just got bitten by this Assertion. The one that starts as in the
subject, and ends with:
"!(((jh2bh(jh))->b_state & (1UL << BH_Lock)) != 0)"
Google reminds me that it was mentioned a few times earlier this year,
but I couldn't find any statement saying that it has been fixed.
I got this in a 2.4.16 kernel, though the
2001 Dec 09
2
New user's naive question
I have installed Mandrake 8.1 and chose ext3 for my main partitions (other
than root). However, stupidly, I cannot now remember whether I specified
ext3 for some other partitions that I haven't yet mounted (these are
essentially just spare capacity, though they may have some files on them if
they weren't formatted).
Is there a simple way of telling whether I should mount these as
2007 Mar 21
3
lock file on embedded device
Hi.
That's my first post. it's driving me crazy.
I'm trying to get dovecot working with vpopmail on Openwrt, an embedded linux-like OS for some routers . So actually my aim looks like get dovecot working with little hardware resources (32 MB of Ram, 8 MB of disk mem.)
I've cross compiled it well(it looks like).
the login against vpopmail works.
using mmap it cannot even select
2002 Dec 15
0
[patch] ext3 use-after-free bugfix
A change was made to ext3 in 2.4.20-pre9 which will cause the
filesystem to run ext3_mark_inode_dirty() against a freed inode.
This will occur when an application attempts to add a new file/directory
to the filesystem and encounters space or inode exhaustion.
The results of this are unpredictable. Usually, nothing happens. But
it can cause random memory corruption on SMP, and the kernel will