similar to: debugfs and ext3 0.0.6b - Bad magic number in super-block

Hello friends, I am trying to learn recovering of file using debugfs. But even though i delete the file and run lsdel in debugfs it always gives me 0 deleted nodes found. Where am i making mistake?. [root at windce7 linux-2.4.32]# fdisk -l Disk /dev/hda: 40.0 GB, 40016019456 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot

I've just set up a brand new system with software raid1 (in degraded mode) with one IDE 20GB drive, using kernel 2.2.19pre16 with ext3 0.0.6b. It's split like this.. 32MB /dev/hda1 /boot 2GB /dev/hda2 / ~18GB /dev/hda3 /home all partitions are marked as 0xfd (autostart raid) with the patches from http://people.redhat.com/mingo/raid-patches for 2.2.17. And I've made all the ext3

Erm, sheez having alot of problems :( I have just been reading all the archives on the mailing list for the past few hours and decided to try make the journal with: tune2fs -j -J10 /dev/hdc1 [root@tkw /]# tune2fs -j -J10 /dev/hdc1 tune2fs 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 Creating journal inode: done [root@tkw /]# cat /etc/fstab /dev/hdc1 /usr/local ext3

Im intending use Ext3 file system in my web farm. Im using RedHat 6.2 (kernel 2.2.16-3) and Turbo Linux Cluster Server 6.0. I have NO SUCCESS in path my own kernel. I downloaded the following ext3 packages: ext3-0.0.2f.tar.gz (linux-2.2.16-3.kdb.diff , linux-2.2.16-3.ext3.diff ) e2fsprogs-1.20-0.WIP.i386.rpm e2fsprogs-1.20-0.WIP.src.rpm e2fsprogs-1.20-0ext3.i386.rpm

Hi everyone, I've been running Redhat 7.2 (new install) for about 2 weeks now without any problems, but today I was not so lucky. My system hung while I was trying to configure the kernel-source RPM using 'xconfig'. After rebooting the system, it seems that my whole ext3 file system is corrupted. I get the message: Mounting root filesystem EXT3-fs: ide0(3,3):couldn't mount

Hi, I'm on kernel 2.14.13-ac8 running Redhat 7.1. I've successfully converted all my file system to ext3 and is working fine for a couple of weeks. However, I did a silly thing when I e2fsck (version 1.23) an ext3 /home partiction without umounting it. Now, I believe my partiton super-block is corrupted and the system wasn't able to mount /home. I tried as suggested to do a e2fsck -b

Hi, We are using the latest ocfs with 11 nodes: OCFS2 Node Manager 1.4.1 Tue Dec 16 19:18:05 PST 2008 (build 0f78045c75c0174e50e4cf0934bf9eae) OCFS2 DLM 1.4.1 Tue Dec 16 19:18:05 PST 2008 (build 4ce8fae327880c466761f40fb7619490) OCFS2 DLMFS 1.4.1 Tue Dec 16 19:18:05 PST 2008 (build 4ce8fae327880c466761f40fb7619490) OCFS2 User DLM kernel interface loaded But we are unable to create files

Hello. We have, over the last few months, lost ext3 filesystems three times. The whole filesystem left unusable. nfs-server:~# mount /dev/rd/c0d1p1 /mnt -t ext3 mount: wrong fs type, bad option, bad superblock on /dev/rd/c0d1p1, or too many mounted file systems (in dmesg) EXT3-fs: journal inode is deleted. EXT3-fs: get root inode failed nfs-server:~# fsck /dev/rd/c0d1p1 Parallelizing

ext3 is having big problems on my x86-64 system. An ext3 partition has just gone crazy, with the following messages in dmesg: EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #4603905: rec_len % 4 != 0 - offset=0, inode=2507704792, rec_len=42, name_len=0 Aborting journal on device hda3. ext3_abort called. EXT3-fs abort (device hda3): ext3_journal_start: Detected aborted journal

Hi, i am having problems converting the rootfs - I created a journal and booted with "rw rootflags=journal=<inode>" - Before i changes the fstab and put the WIP fsck to /sbin/fsck.ext3. The kernel seems to mount the filesystem ok and then the bootup scripts (debian potato) try to fsck the rootfs which leads to e2fsck 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 JFS DEBUG:

Hi, I just tried the 2.6.22-r1 candidate to test whether some bug I have hit in the past still exists. I did use 2.6.20.6 so far. So, I have cleanly rebooted to use the new kernel, after the machine came up I tried to mess with the bug, and had to reboot again to play with kernel commandline parameters. Unfortunately, on the next reboot fsck was schedules on my filesystem after 38 clean

On Thu, 2024-10-03 at 23:48 +0200, Danilo Krummrich wrote: > > +#ifdef CONFIG_DEBUG_FS > > + /* > > + * Logging buffers in debugfs. The wrapper objects need to remain > > + * in memory until the dentry is deleted. > > + */ > > + struct dentry *dir; /* Parent dentry */ > > + struct dentry *dir_init; > > + struct dentry *dir_rm; > > + struct

I must profane ignorance of complicated filesystem stuff, so feel free to call me out here. Booting a root ext3 drive produces the following message at boot: kinit: trying to mount /dev/root on /root with type ext2 EXT2-fs warning (device hda3): ext2_fill_super: warning: mounting ext3 filesystem as ext2 When remounted rw by init, everything looks fine: $ mount | grep hda3 /dev/hda3 on / type

Typically DRM drivers use the DRM debugfs root entry. However, since Nouveau is heading towards a split into a core and a DRM driver, create a module specific debugfs root directory. Subsequent patches make use of this new debugfs root in order to store GSP-RM log bufferes (optionally beyond a device driver binding). Signed-off-by: Danilo Krummrich <dakr at kernel.org> --- Unless there are

On Sat, 2024-08-03 at 02:00 +0200, Danilo Krummrich wrote: > > +???????/* Each GPU has a subdir based on its device name, so find it */ > > +???????struct drm_device *drm_dev = dev_get_drvdata(dev); > > In drm-misc-next dev_get_drvdata() returns a struct nouveau_drm. > Interestingly, > things do not blow up however. > > Instead, I noticed that your debugfs entries

On 11/25/24 5:55 PM, Timur Tabi wrote: > On Mon, 2024-11-25 at 15:25 +0100, Danilo Krummrich wrote: >> Typically DRM drivers use the DRM debugfs root entry. However, since >> Nouveau is heading towards a split into a core and a DRM driver, create >> a module specific debugfs root directory. >> >> Subsequent patches make use of this new debugfs root in order to

On Saturday I finally upgraded a machine from CentOS 4.3 (I think) to 4.5 via yum. Seemed to went fine. However, during the following night /home got mounted read-only because of an EXT3-fs error. The next night happened the same. Also, today, I saw the first-ever kernel crash on this machine. The machine is about three years old or so, went into production two years ago with CentOS 4.1 or so and

I'm using the ext3-patched version of Linux 2.4.13 (the patch from Andrew Morton's UOW site). I compiled both ext3 and ext2 into the kernel. I've also done "tune2fs -j /dev/hda3" and changed /etc/fstab to ext3. However, when I boot up, the filesystem still gets mounted as ext2. I've been trying to figure out why for many days now.. any ideas? Here's my setup:

debugfs.h protects itself from an undefined DEBUG_FS, so it is not necessary to check it in the driver code or the Makefile. The driver code had been updated for this, but the Makefile had missed the update. Link: https://lore.kernel.org/linux-next/fec68c3c-8249-7af4-5390-0495386a76f9 at infradead.org/ Fixes: a16291b5bcbb ("pds_vdpa: Add new vDPA driver for AMD/Pensando DSC")

Export initrd in debugfs when retained. As a side effect, initrd_start and initrd_end are not cleared when the initrd is retained. After this patch, one can then copy the initrd space from debugfs and pass it to kexec as the initrd, or do something else with it (maybe it was an initrd not an initramfs). Signed-off-by: Milton Miller <miltonm at bga.com> --- This is a lot more reliable