User talk:Cattelan - Revision history

Cattelan: Cattelan moved page User talk:Anshul.kundra to User talk:Cattelan: Automatically moved page while merging the account "Anshul.kundra" to "Cattelan"

2021-05-17T04:08:13Z

Cattelan moved page User talk:Anshul.kundra to User talk:Cattelan: Automatically moved page while merging the account "Anshul.kundra" to "Cattelan"

← Older revision		Revision as of 04:08, 17 May 2021
(No difference)

Ckujau: reply

2012-10-19T19:07:55Z

← Older revision		Revision as of 19:07, 19 October 2012
Line 84:		Line 84:
	Thanks & Best Regards		Thanks & Best Regards
	Anshul Kundra		Anshul Kundra
			: Anshul, as I have suggested [[User:Anshul.kundra\|earlier]]: please ask questions on the [[XFS_email_list_and_archives\|mailing lists]]. Also, your question [https://encrypted.google.com/search?hl=en&q=vi%20inode%20change has been answered many times] already. -- [[User:Ckujau\|Ckujau]] ([[User talk:Ckujau\|talk]]) 19:07, 19 October 2012 (UTC)

Cattelan: /* XFS File Inode number is changing using the utilities */ new section

2012-10-19T14:34:54Z

XFS File Inode number is changing using the utilities: new section

← Older revision		Revision as of 14:34, 19 October 2012
Line 11:		Line 11:
	ERS		ERS
	: Has been answered on the [http://www.spinics.net/lists/xfs/msg09007.html mailinglist] -- [[User:Ckujau\|Ckujau]] 23:39, 16 February 2012 (UTC)		: Has been answered on the [http://www.spinics.net/lists/xfs/msg09007.html mailinglist] -- [[User:Ckujau\|Ckujau]] 23:39, 16 February 2012 (UTC)

			== XFS File Inode number is changing using the utilities ==


			To Developers,

			I have seen a different behaviour in XFS

			Suppose I have a file with inode number "131", I have noticed that the inode number of file got changed without deleting the file. When we change the data of the file everytime it changes the inode number. The complete description over the test is as follows

			Steps are as follows:

			1) I have created a file using "dd" of size 100MB:

			#dd if=/dev/zero of=xfs.img bs=1M count=100

			2) Created a loopback device over the image:
			#losetup /dev/loop1 xfs.img

			3) Created file system:
			#mkfs.xfs /dev/loop1

			4) Mounted:
			#mount /dev/loop1 /mnt/xfs_mnt

			5) Please check the mount output:
			# mount

			/dev/sdb2 on / type ext3 (rw,acl,user_xattr)
			proc on /proc type proc (rw)
			sysfs on /sys type sysfs (rw)
			debugfs on /sys/kernel/debug type debugfs (rw)
			devtmpfs on /dev type devtmpfs (rw,mode=0755)
			tmpfs on /dev/shm type tmpfs (rw,mode=1777)
			devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
			fusectl on /sys/fs/fuse/connections type fusectl (rw)
			rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
			/dev/loop0 on /mnt/mount_test type xfs (rw)
			/dev/loop1 on /mnt/xfs_mnt type xfs (rw)

			6) Created a file using "touch"

			# touch kundra.txt

			7) Checking the file and its inode number:

			# ls -li
			total 0
			131 -rw-r--r-- 1 root root 0 2012-10-20 01:41 kundra.txt

			8) I have written some data using the vim editor, I can't provide snapshot of vim on the list:

			#vim kundra.txt

			9) Now I checked the inode number using the "ls -li"
			# ls -li

			total 4
			133 -rw-r--r-- 1 root root 19 2012-10-20 01:43 kundra.txt

			Please check that the inode number ( from "131" to "133" ) and total value (from "0" to "4" )in the filesystem got changed, I am assuming that the reasom may be due to filesystem of small size but it is showing unexpected behaviour.

			Please provide some description over this issue, I am working on Linux SLES

			# cat /etc/issue

			Welcome to SUSE Linux Enterprise Server 11 SP1 (x86_64) - Kernel \r (\l).

			# uname -a
			Linux linux-sles 2.6.32.19-0.6-default #1 SMP Fri Aug 31 01:37:50 IST 2012 x86_64 x86_64 x86_64 GNU/Linux

			Thanks & Best Regards
			Anshul Kundra

Ckujau: see http://www.spinics.net/lists/xfs/msg09007.html

2012-02-16T23:39:25Z

see http://www.spinics.net/lists/xfs/msg09007.html

← Older revision		Revision as of 23:39, 16 February 2012
Line 1:		Line 1:
			== XFS_IOCORE_R ==

	To Developers ,		To Developers ,
	I have read about the new member named as xfs_extdelta that is passed in different xfs internal routines i.e xfs_bmapi , In the 2.4 versions instead of using it is just passed as NULL can anyone provide info regarding that where to initialize and if I pass it NULl then is there any adverse effect of it		I have read about the new member named as xfs_extdelta that is passed in different xfs internal routines i.e xfs_bmapi , In the 2.4 versions instead of using it is just passed as NULL can anyone provide info regarding that where to initialize and if I pass it NULl then is there any adverse effect of it
Line 8:		Line 10:
	HCL TECHNOLOGIES		HCL TECHNOLOGIES
	ERS		ERS
			: Has been answered on the [http://www.spinics.net/lists/xfs/msg09007.html mailinglist] -- [[User:Ckujau\|Ckujau]] 23:39, 16 February 2012 (UTC)

Cattelan: XFS information query

2012-01-11T15:44:33Z

XFS information query

New page

To Developers ,
I have read about the new member named as xfs_extdelta that is passed in different xfs internal routines i.e xfs_bmapi , In the 2.4 versions instead of using it is just passed as NULL can anyone provide info regarding that where to initialize and if I pass it NULl then is there any adverse effect of it

XFS_IOCORE_RT not been used in 2.6 version , so if instead of this flag I will pass XFS_IOCORE_EXCL it will be ok or will cause any crash or adverse effects or either there is any alternative present to sought out from these two problems

Regards
Anshul Kundra
HCL TECHNOLOGIES
ERS