search for: half_md4

...xt check after: Mon Feb 24 07:30:10 2014 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: ad2251a9-ac33-4e5e-b933-af49cb4f2bb3 Journal backup: inode blocks $ df --block-size=1 /dev/mapper/datavg-datalogslv Filesystem 1B-blocks Used Available Use% Mounted on /dev/mapper/datavg-datalogslv 13243846656 563843072 12007239680...

...s uid: 0 (user root) >> Reserved blocks gid: 0 (group root) >> First inode: 11 >> Inode size: 256 >> Required extra isize: 28 >> Desired extra isize: 28 >> Journal inode: 8 >> Default directory hash: half_md4 >> Directory Hash Seed: ad2251a9-ac33-4e5e-b933-af49cb4f2bb3 >> Journal backup: inode blocks >> >> $ df --block-size=1 /dev/mapper/datavg-datalogslv >> Filesystem 1B-blocks Used Available Use% Mounted on >> /dev/mapper/d...

...:10 2014 > Reserved blocks uid: 0 (user root) > Reserved blocks gid: 0 (group root) > First inode: 11 > Inode size: 256 > Required extra isize: 28 > Desired extra isize: 28 > Journal inode: 8 > Default directory hash: half_md4 > Directory Hash Seed: ad2251a9-ac33-4e5e-b933-af49cb4f2bb3 > Journal backup: inode blocks > > $ df --block-size=1 /dev/mapper/datavg-datalogslv > Filesystem 1B-blocks Used Available Use% Mounted on > /dev/mapper/datavg-datalogslv 132438...

...t;>> Reserved blocks gid: 0 (group root) >>> First inode: 11 >>> Inode size: 256 >>> Required extra isize: 28 >>> Desired extra isize: 28 >>> Journal inode: 8 >>> Default directory hash: half_md4 >>> Directory Hash Seed: ad2251a9-ac33-4e5e-b933-af49cb4f2bb3 >>> Journal backup: inode blocks >>> >>> $ df --block-size=1 /dev/mapper/datavg-datalogslv >>> Filesystem 1B-blocks Used Available Use% Mounted on &g...

Hello, I have a problem with directories that contain more than 10000 entries (Ubuntu 8.04.1) or with more than 70000 entries (RHEL 5.2). If you use readdir(3) or readdir64(3) you get one entry twice, with same name and inode. Some analyzing showed that disabling dir_index solves this problem, but I think that this is a bug in the ext3 code, as no other file-system shows this behavior.

...ks gid: 0 (group root) >>>> First inode: 11 >>>> Inode size: 256 >>>> Required extra isize: 28 >>>> Desired extra isize: 28 >>>> Journal inode: 8 >>>> Default directory hash: half_md4 >>>> Directory Hash Seed: ad2251a9-ac33-4e5e-b933-af49cb4f2bb3 >>>> Journal backup: inode blocks >>>> >>>> $ df --block-size=1 /dev/mapper/datavg-datalogslv >>>> Filesystem 1B-blocks Used Availabl...

...es: 61 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 First orphan inode: 1439005 Default directory hash: half_md4 Directory Hash Seed: f7476ad6-3067-4697-93b3-f4a368d76eab Journal backup: inode blocks Journal superblock magic number invalid! root at T60:~# Am I correct that there are multiple super-blocks scattered around the HDD and if first one is missing, then next one is read by file or du...

On 8/17/14, 12:28 PM, Roland Olbricht wrote: > Hello everybody, > > first of all thank you the development of Ext2/3/4. It works like a > charm and makes it possible to base applications on it. > However, "df" says: > > Filesystem 1K-blocks Used Available Use% Mounted on > ... > /dev/sdc 468346644 409888536 35015532 93% /opt/ssd >

...133 MB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 First orphan inode: 8388637 Default directory hash: half_md4 Directory Hash Seed: a094608e-671f-4a9c-81e8-81bb72eb4516 Journal backup: inode blocks Journal features: journal_incompat_revoke Journal size: 128M Journal length: 32768 Journal sequence: 0x001d92ff Journal start: 27755 > It could...

Hello everybody, first of all thank you the development of Ext2/3/4. It works like a charm and makes it possible to base applications on it. However, now I have the first time where I need more information to understand the behaviour of a ext4 installation on a 480 GB harddisk. It holds a database with a size of 355 GB, as said by "du -m": ... 355263 /opt/ssd However,

...ot) >>>>> First inode: 11 >>>>> Inode size: 256 >>>>> Required extra isize: 28 >>>>> Desired extra isize: 28 >>>>> Journal inode: 8 >>>>> Default directory hash: half_md4 >>>>> Directory Hash Seed: ad2251a9-ac33-4e5e-b933-af49cb4f2bb3 >>>>> Journal backup: inode blocks >>>>> >>>>> $ df --block-size=1 /dev/mapper/datavg-datalogslv >>>>> Filesystem 1B-blocks...

On Monday 24 November 2014 16:22:53 Hu Tao wrote: > On Fri, Nov 21, 2014 at 05:17:13PM +0100, Pino Toscano wrote: > > On Friday 21 November 2014 13:18:00 Hu Tao wrote: > > > btrfs_subvolume_show shows the detailed information of a subvolume > > > or > > > snapshot. > > > > > > Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> > > >

...t check after: Fri Apr 25 21:38:53 2014 Lifetime writes: 14 TB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Default directory hash: half_md4 Directory Hash Seed: 37c55228-9d7b-4a34-bd88-8322f435b9cb Journal backup: inode blocks -- kkeller@wombat.san-francisco.ca.us

We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but neither one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS. I know there are different methods for formatting large disks but this one doesn't even seem to show up as a /dev/

Hi - Updated my old project named "ext3carve" and renamed it as "extcarve" . It uses libext2fs. (To be precise,re-uses on 'debugfs' command's "dump_unused" feature) In summary,the tool will do the following - It will scan the linux machine ,for unused/deleted blocks and search for magic signatures. If it finds valid signature (both header and footer) It

Today, I had to uncleanly shutdown one of our machines due to an error in 2.6.28.3. Durin the boot sequence, the ext4 partition /home experienced a journal replay. /home looks like this: /dev/mapper/volg1-logv1 on /home type ext4 (rw,noexec,nodev,noatime,errors=remount-ro) Filesystem Size Used Avail Use% Mounted on /dev/mapper/volg1-logv1 2,4T 1,4T 1022G 58% /home Filesystem