Displaying 20 results from an estimated 400 matches similar to: "How to read group descriptor?"
2008 Mar 20
1
How to get device name with device id?
Hi all,
I want to open a device(/dev/sda1, /dev/hda2 etc) in which my file exists.
I've used 'stat' system call to get the device id.
But now I want the device name from this id(st_dev).
How to get that one?
Or
Do you have any other method to know the device name where my file resides?
Thanks
Bollywood, fun, friendship, sports and more. You name it, we have it on
2002 Apr 02
0
[patch] fix ext3 i_blocks accounting
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
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.
2008 Oct 11
1
[PATCH] fstype: Fix ext4/ext4dev probing
Enhance fstype so it properly takes into account whether or not the
ext4 and/or ext4dev filesystems are present, and properly handles the
test_fs flag. The old code also has some really buggy checks --- for
example, where it compared the set of supported ro_compat features
against the incompat feature bitmask:
(sb->s_feature_incompat & __cpu_to_le32(EXT3_FEATURE_RO_COMPAT_SUPP)
I
2003 Jun 12
2
How can I read superblock(ext2, ext3)'s information?
Hello,
I'd like to read superblock's information on Redhat 7.3,
but I don't know how to do it.
For example,
Input : "/dev/sdj2"
Output : ext2_super_block struct's s_wtime
(I saw it at "/usr/include/ext2fs/ext2_fs.h")
Input : "/dev/sdj1"
Output : ext3_super_block struct's s_wtime
(I saw it at
2011 Dec 14
2
[LLVMdev] Generating superblocks (SEME regions w/o loops and calls) in LLVM
Hi all,
While developing compile-time instrumentation for ThreadSanitizer
(http://code.google.com/p/data-race-test) I need to generate SEME
regions without loop and call instructions
(I'll call them superblocks hereafter, although some researchers do
allow loops in their definition of superblocks).
This is necessary to get the largest piece of IR in which the memory
operations can be
2012 May 03
1
[PATCH] Btrfs: fix crash in scrub repair code when device is missing
Fix that when scrub tries to repair an I/O or checksum error and one of
the devices containing the mirror is missing, it crashes in bio_add_page
because the bdev is a NULL pointer for missing devices.
Reported-by: Marco L. Crociani <marco.crociani@gmail.com>
Signed-off-by: Stefan Behrens <sbehrens@giantdisaster.de>
---
fs/btrfs/scrub.c | 7 +++++++
1 file changed, 7 insertions(+)
2008 Jun 16
0
latest fixes
hello hpa,
nothing too exciting,
again syncing latest Debian upload and subsequent patch emails.
plus wanting to get the ext4dev in line for the Lenny release. :)
please review.
thanks
--
maks
please pull
git pull git://git.debian.org/~maks/klibc.git maks
for the changes:
Arthur Loiret (1):
Makefile (ARCH): Support sh4 as sh.
David H?rdeman (1):
[klibc] mount: allow multiple fs
2019 Oct 07
0
[klibc:master] fstype: Drop obsolete support for "ext4dev"
Commit-ID: 52251e210c7a21068063fe16a3874903d3f1aa14
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=52251e210c7a21068063fe16a3874903d3f1aa14
Author: Ben Hutchings <ben at decadent.org.uk>
AuthorDate: Mon, 7 Oct 2019 20:39:46 +0100
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Tue, 8 Oct 2019 00:13:20 +0100
[klibc] fstype: Drop obsolete
2015 Jan 06
2
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
On 01/06/2015 08:04 AM, H. Peter Anvin wrote:
> On 01/01/2015 09:05 PM, Robert Yang wrote:
>> Hello,
>>
>> Happy New Year!
>>
>> These patches make syslinux/linux support ext2/3/4, and it doesn't
>> require the root privilege, I'd like to add a separate e2fs/syslinux, if
>> that is more appropriate, it should be easy to do that.
>>
2015 Jan 06
3
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
On 01/06/2015 08:16 AM, H. Peter Anvin wrote:
> On 01/05/2015 04:14 PM, Robert Yang wrote:
>>
>> On 01/06/2015 08:04 AM, H. Peter Anvin wrote:
>>> On 01/01/2015 09:05 PM, Robert Yang wrote:
>>>> Hello,
>>>>
>>>> Happy New Year!
>>>>
>>>> These patches make syslinux/linux support ext2/3/4, and it doesn't
2015 Jun 12
4
[LLVMdev] Loop Vectorization and Store-Load Forwarding issue
I have been looking into this small test case (Part A) where loop vectorization is disabled due to possible store-load forwarding conflict (Part B). As you can see, due to the presence of dependence distance 2 the loop is vectorizable only for a width of 2. However, the presence of dependence distance 15 (due to y[j-15]) results in store-load forwarding issue as store packet of y[16:17] (iteration
2015 Sep 28
2
parse raw image to read block group desc table!
Hi,
I am writing a piece of code to open a raw image file of a virtual machine
which has ubuntu installed in it. The virtual disk is formatted using MBR
partitioning method and has 3 primary and 1 extended partition.
I want to open up that file and read the block group descriptor table and
inode table for each partition. I have written some lines of code and
successfully able to read the
2015 Jan 06
0
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
On 01/05/2015 04:14 PM, Robert Yang wrote:
>
> On 01/06/2015 08:04 AM, H. Peter Anvin wrote:
>> On 01/01/2015 09:05 PM, Robert Yang wrote:
>>> Hello,
>>>
>>> Happy New Year!
>>>
>>> These patches make syslinux/linux support ext2/3/4, and it doesn't
>>> require the root privilege, I'd like to add a separate e2fs/syslinux, if
2015 Jan 06
0
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
On 01/05/2015 07:20 PM, Robert Yang wrote:
>
> Hello,
>
> After more investigations, I'm a little worried about add the extX support
> to mtools/syslinux:
> 1) Its name is mtools/syslinux, can't express the libext2fs.
Renaming it is not a problem.
> 2) The mtools/syslinux isn't fully functioned, for example, as the code
> shows:
> if (opt.sectors ||
2015 Jan 06
0
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
On 01/01/2015 09:05 PM, Robert Yang wrote:
> Hello,
>
> Happy New Year!
>
> These patches make syslinux/linux support ext2/3/4, and it doesn't
> require the root privilege, I'd like to add a separate e2fs/syslinux, if
> that is more appropriate, it should be easy to do that.
>
> I put these patches on github so that you can easily get them in case
>
2005 Jan 06
0
[2.6 patch] fs/ext3/: possible cleanups
The patch below contains the following cleanups:
- make some needlessly global code static
- super.c: remove the unused global function ext3_panic
Please comment ib whether this patch is correct or conflicts with
pending changes.
diffstat output:
fs/ext3/balloc.c | 2
fs/ext3/dir.c | 2
fs/ext3/inode.c | 4
fs/ext3/resize.c | 4
2014 Dec 25
2
[PATCH 0/8] extlinux: support unmounted ext2/3/4 filesystem
On 12/25/2014 04:33 AM, H. Peter Anvin wrote:
> On 12/24/2014 12:16 AM, Robert Yang wrote:
>> Hello syslinux,
>>
>> Merry Christmas! These patches will make extlinux work with umounted
>> ext2/3/4 filesystem, for example:
>>
>> $ extlinux -i /dev/sdXN
>> or
>> $ extlinux -i file_block
>>
>> Also it can work with something like:
2003 Aug 16
7
sharing an ext3-partition with windows?
Hello,
is anyone successfully sharing a ext3 partition between windows and linux?
Which software do you use under (which) windows? Was it easy to setup?
TIA and Regards,
Helge
2015 Jan 06
2
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
On 01/07/2015 03:47 AM, H. Peter Anvin wrote:
> On 01/05/2015 07:20 PM, Robert Yang wrote:
>>
>> Hello,
>>
>> After more investigations, I'm a little worried about add the extX support
>> to mtools/syslinux:
>> 1) Its name is mtools/syslinux, can't express the libext2fs.
>
> Renaming it is not a problem.
Do you have any suggestion about the new