On 2018年01月18日 13:27, Ilan Schwarts wrote:
> Is there a way to retrieve this anonymous device number ?
No. Because returning device number on stat() call is already a stupid
idea for any fs without consistent single device.
For btrfs, it's because btrfs has multiple device and even for single
On 2018年01月17日 22:36, Ilan Schwarts wrote:
> Hi,
> A new questions for this thread. Thanks in advance.
>
> Given a result from stat:
> builder@SLES12X86-64:~> stat /home/builder/myfile1
> File: ‘/home/builder/myfile1’
> Size: 0 Blocks: 0 IO Block: 4096 regular empty
Hi,
A new questions for this thread. Thanks in advance.
Given a result from stat:
builder@SLES12X86-64:~> stat /home/builder/myfile1
File: ‘/home/builder/myfile1’
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 31h/49d Inode: 549453 Links: 1
I underst
On 2018年01月15日 20:08, Ilan Schwarts wrote:
> Thanks for detailed information !
> Its a legacy code for kernel module i maintain.. dont talk to me about
> ancient when i need to maintain it to systems like solaris 8 or RHEL4
> 2.6.9 :(
Well, that's unfortunate, I mean real unforunate...
Despite
Thanks for detailed information !
Its a legacy code for kernel module i maintain.. dont talk to me about
ancient when i need to maintain it to systems like solaris 8 or RHEL4
2.6.9 :(
On Mon, Jan 15, 2018 at 12:01 PM, Qu Wenruo wrote:
>
>
> On 2018年01月15日 17:24, Ilan Schwarts wrote:
>> Qu,
>> G
On 2018年01月15日 17:24, Ilan Schwarts wrote:
> Qu,
> Given inode, i get the fsid via: inode->i_sb->s_dev;
> this return dev_t and not u8/u16
That's just a device number.
Not really useful in btrfs, since btrfs is a multi-device filesystem.
Thanks,
Qu
>
>
> On Sun, Jan 14, 2018 at 12:44 PM, Qu
On 2018年01月15日 17:05, Ilan Schwarts wrote:
> Qu, Thank you very much for detailed response.
>
> I would like to understand something, on VFS, it is guaranteed that in
> a given filesystem, only 1 inode number will be used, it is unique.> In
> btrfs, you say the inode uniqueness is per volume, e
Qu,
Given inode, i get the fsid via: inode->i_sb->s_dev;
this return dev_t and not u8/u16
On Sun, Jan 14, 2018 at 12:44 PM, Qu Wenruo wrote:
>
>
> On 2018年01月14日 18:32, Ilan Schwarts wrote:
>> Thank you for clarification.
>> Just 2 quick questions,
>> 1. Sub volumes - 2 sub volumes cannot have
Qu, Thank you very much for detailed response.
I would like to understand something, on VFS, it is guaranteed that in
a given filesystem, only 1 inode number will be used, it is unique.
In btrfs, you say the inode uniqueness is per volume, each volume has
its own inode space, How is it possible ?
On 2018年01月14日 18:32, Ilan Schwarts wrote:
> Thank you for clarification.
> Just 2 quick questions,
> 1. Sub volumes - 2 sub volumes cannot have 2 same inode numbers ?
They can.
So to really locate an inode in btrfs, you need:
fsid (locate the fs) -> subvolume id (locate subvolume) -> inode nu
On Sun, Jan 14, 2018 at 12:32:25PM +0200, Ilan Schwarts wrote:
> Thank you for clarification.
> Just 2 quick questions,
> 1. Sub volumes - 2 sub volumes cannot have 2 same inode numbers ?
Incorrect. You can have two subvolumes of the same filesystem, and
you can have files with the same inode n
Thank you for clarification.
Just 2 quick questions,
1. Sub volumes - 2 sub volumes cannot have 2 same inode numbers ?
2. Why fsInfo fsid return u8 and the traditional file system return
dev_t, usually 32 integer ?
On Sun, Jan 14, 2018 at 12:22 PM, Qu Wenruo wrote:
>
>
> On 2018年01月14日 18:13, Il
On 2018年01月14日 18:13, Ilan Schwarts wrote:
> both btrfs filesystems will have same fsid ?
>
>
> On Sun, Jan 14, 2018 at 12:06 PM, Ilan Schwarts wrote:
>> But both filesystems will have same fsid?
>>
>> On Jan 14, 2018 12:04, "Nikolay Borisov" wrote:
>>>
>>>
>>>
>>> On 14.01.2018 12:02, Ilan S
both btrfs filesystems will have same fsid ?
On Sun, Jan 14, 2018 at 12:06 PM, Ilan Schwarts wrote:
> But both filesystems will have same fsid?
>
> On Jan 14, 2018 12:04, "Nikolay Borisov" wrote:
>>
>>
>>
>> On 14.01.2018 12:02, Ilan Schwarts wrote:
>> > First of all, Thanks for response !
>> >
On 14.01.2018 12:02, Ilan Schwarts wrote:
> First of all, Thanks for response !
> So if i have 2 btrfs file system on the same machine (not your
> everyday scenario, i know)
> Lets say a file is created on device A, the file gets inode number X
> is it possible on device B to have inode number X
First of all, Thanks for response !
So if i have 2 btrfs file system on the same machine (not your
everyday scenario, i know)
Lets say a file is created on device A, the file gets inode number X
is it possible on device B to have inode number X also ?
or each device has its own Inode number range ?
On 2018年01月14日 16:33, Ilan Schwarts wrote:
> Hello btrfs developers/users,
>
> I was wondering regarding to fetching the correct fsid on btrfs from
> the context of a kernel module.
There are two IDs for btrfs. (in fact more, but you properly won't need
the extra ids)
FSID: Global one, one fs
On 2018年01月14日 16:33, Ilan Schwarts wrote:
> Hello btrfs developers/users,
>
> I was wondering regarding to fetching the correct fsid on btrfs from
> the context of a kernel module.
There are two IDs for btrfs. (in fact more, but you properly won't need
the extra ids)
FSID: Global one, one fs
Hello btrfs developers/users,
I was wondering regarding to fetching the correct fsid on btrfs from
the context of a kernel module.
if on suse11.3 kernel 3.0.101-0.47.71-default in order to get fsid, I
do the following:
convert inode struct to btrfs_inode struct (use btrfsInode =
BTRFS_I(inode)), t
19 matches
Mail list logo
