DBCC LOGINFO

Follow the link for better knowledge on log file information
http://www.simple-talk.com/sql/database-administration/sql-server-transaction-log-fragmentation-a-primer/

Deeper Look at DBCC LOGINFO

Run the DBCC LOGINFO and each one representing a VLF

FileId   FileSize      StartOffset      FSeqNo    Status      Parity CreateLSN
-------- ------------- ---------------- ---------- ---------- ------ ---------
2        253952         8192            30        2           64     0
2        253952         262144          0         0           0      0
2        253952         516096          0         0           0      0
2        278528         770048          0         0           0      0

These columns have the following meaning:

• FileID – the FileID number as found in sysfiles
• FileSize – the size of the VLF in bytes
• StartOffset – the start of the VLF in bytes, from the front of the transaction log
• FSeqNo – indicates the order in which transactions have been written to the different VLF files. The VLF with the highest number is the VLF to which log records are currently being written.
• Status – identifies whether or not a VLF contains part of the active log. A value of 2 indicates an active VLF that can't be overwritten.
• Parity – the Parity Value, which can be 0, 64 or 128 (see the Additional Resources section at the end of this article for more information)
• CreateLSN – Identifies the LSN when the VLF was created. A value of zero indicates that the VLF was created when the database was created. If two VLFs have the same number then they were created at the same time, via an auto-grow event.